-
Notifications
You must be signed in to change notification settings - Fork 102
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
Updated Dev Guide to describe current CI workflows #1724
Conversation
@adrienbernede do have any thoughts on what's going on with the RAJA poodle jobs? They have been dying in the resource allocation part since last week. I posted a message in LLNL GitLab channel on Mattermost, but no response yet. |
I also asked yesterday. Although it looked like a failing allocation, the job log suggested a runner issue. I checked that poodle was up before reaching out for help. It should be OK now, but one less runner increases the competition. |
Folks, this is ready to merge. Please review. |
@adrienbernede there is a response on mattermost to my post. it looks like they don't understand the issue with the poodle18 runner. |
docs/sphinx/dev_guide/ci.rst
Outdated
While we do some GPU builds on Azure, RAJA tests are only run for CPU-only | ||
builds. The current set of builds run on Azure can be seen by looking at | ||
the ``RAJA/azure-pipelines.yml`` and ``RAJA/Dockerfile`` files. | ||
The RAJA project uses threes CI tools to run tests: |
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.
Should this be "uses three CI tools" instead of "threes"?
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.
Good catch. Fixed.
…A into task/rhornung67/devguide-update
Summary
The generated RTD documentation for this PR branch is here: https://raja.readthedocs.io/en/task-rhornung67-devguide-update/sphinx/dev_guide/index.html