fix: shift to brycecanyon, craterlake #487
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
topic: documentation
veprbl
approved these changes
Jul 20, 2023
|
Strange, but craterlake leads to reconstruction benchmark failures for the ecal endcap positive, https://eicweb.phy.anl.gov/EIC/benchmarks/reconstruction_benchmarks/-/jobs/1791231... |
|
I'm going to force-merge this because right now we have a README.md with all kinds of borken links that point to craterlake artifacts that don't exist until this is merged... But it's clear no PR can succeed the CI pipelines for craterlake until this is investigated and fixed... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Briefly, what does this PR introduce?
This switches the README.md and CI pipelines from arches/brycecanyon to brycecanyon/craterlake.
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No.
Does this PR change default behavior?
No.