-
Notifications
You must be signed in to change notification settings - Fork 27
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
V0.7.0 rc #916
Conversation
The bug was caused by re-using the ISendRequest before the request completed.
This is a step toward eventually shifting the communication code to conduit. The current computeClosestPoint still works.
Converted SLIC's logger container and active-logger pointer to a singleton class to guard against problems with initialization. Co-authored-by: Rich Hornung <hornung1@llnl.gov>
…und. It doesn't work in conjuction with thresholding, which is more effective.
…to our export list
Object mesh should not depend on number of MPI processes. Remove debug code.
This helps reduce memory use by non-blocking sends.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bmhan12 !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
update SCR link
* Add CUDA option to using-with examples, add Serac workaround for cmake example * Add HIP option to using-with examples, add -lblt_hip_runtime workaround for cmake example Co-authored-by: Chris White <white238@llnl.gov>
Looking to merge into main, but there are these two required checks in Azure that are still waiting for status to be reported:
These might be from main? These jobs don't appear in the triggered Azure run, as the |
@bmhan12 you are correct in that the azure builds for the main branch do gcc8, while develop (and this RC branch) do gcc11. I don't know how to resolve this. I would think that the CI would run on a version of the code with this branch merged into main. |
@white would probably know. |
I was trying to see if maybe starting a run through Azure Pipelines GUI instead of triggered by commit would solve the issue, but I don't have that access in Azure. Can someone grant me access? |
CI will run the jobs that are in the branch but Github protects the branch on specific jobs (which this branch is not running). The way around this is to verify manually we are okay with merging, then have an authorized person turn off the specific branch protection for these tests, merge, then turn on the new ones for future PRs. This is to stop someone from turning off checks to get their PR in. |
I don't think we should do a small PR to main to update the CI since that would pollute main, which should only contain merges that reflect the release history. Let's do what Chris suggested. @bmhan12 please verify that the RC branch works on a TOSS system with gcc8. Then, we can turn off the branch permissions on main and merge the PR. |
Yes, as part of gitlab we test gcc 8 on ruby (TOSS3): https://lc.llnl.gov/gitlab/axom/axom/-/pipelines/203905 EDIT: I've also verified gcc 8 passes as part of running |
This PR: