Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check upstream master branches for PMIx/PRRTE #12885

Closed
wants to merge 2 commits into from

Conversation

rhc54
Copy link
Contributor

@rhc54 rhc54 commented Oct 28, 2024

No description provided.

@rhc54 rhc54 marked this pull request as draft October 28, 2024 15:07
@rhc54 rhc54 added the mpi4py-all Run the optional mpi4py CI tests label Oct 30, 2024
@rhc54
Copy link
Contributor Author

rhc54 commented Oct 30, 2024

@janjust @bwbarrett Could someone help me understand the "continuous-integration/jenkins" failure report? When I click on "Details", it shows a green check by every stage of the procedure - which to me, at least, implies like it "passed". I don't see anything saying it failed.

Is there some subtle thing I'm supposed to notice???

@janjust janjust removed the mpi4py-all Run the optional mpi4py CI tests label Oct 30, 2024
@rhc54
Copy link
Contributor Author

rhc54 commented Oct 30, 2024

Hit the "console" button and see some weird error output saying that configure cannot find PMIx??? This is very confusing.

@jsquyres
Copy link
Member

jsquyres commented Oct 30, 2024

Could someone help me understand the "continuous-integration/jenkins" failure report?

Yeah, it's a little less than obvious. We haven't found a way to make it better. What you have to do is:

  1. Click the Details link to go to the Jenkins report. It shows the "all green" output, which makes you think it passed. But it didn't.
  2. In the top-left of the screen, click on the build number. In this case, it's "3" (i.e., the 3rd build of this PR).
  3. In the page that comes up, click on "Pipeline steps" in the left-hand navigation.

From here, you'll see steps that have a red X / failed.

In this case, it looks like they had the dumb fail-to-git-clone error that still happens sometimes. Sigh. This is just a bot retest type of situation.

@jsquyres
Copy link
Member

bot:ompi:retest

@janjust janjust added the mpi4py-all Run the optional mpi4py CI tests label Oct 30, 2024
@rhc54
Copy link
Contributor Author

rhc54 commented Oct 30, 2024

I surrender - just cannot get this pulled from upstream

@rhc54 rhc54 closed this Oct 30, 2024
@rhc54 rhc54 deleted the topic/chk branch October 30, 2024 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mpi4py-all Run the optional mpi4py CI tests Target: main
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants