-
Notifications
You must be signed in to change notification settings - Fork 82
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
Trivial change to test CI system on a non-master branch. #263
Conversation
Hi @kutschke,
which require these tests: build. @Mu2e/write, @Mu2e/mu2eii_sm21_ci have access to CI actions on Mu2eII_SM21. ⌛ The following tests have been triggered for 38884e6: build (Build queue has 6 jobs) |
☔ The tests failed for ref 38884e6.
For more information, please check the job page here. Logfiles may also be accessed at this link. |
@FNALbuild run build tests |
❌ Those tests have already run or are running for 38884e6 (build) |
@FNALbuild run build tests |
1 similar comment
@FNALbuild run build tests |
⌛ The following tests have been triggered for 4ebe06c: build (already triggered: build) (Build queue has 5 jobs) |
☀️ The tests passed at ref 4ebe06c.
For more information, please check the job page here. Logfiles may also be accessed at this link. |
Note that g4test_03 failed on the first test but passed the second. The only change was to a string literal inside HelloWorld, which was needed to force the system to rerun the tests. I remember this happening before. Added issue #266 to report the intermittent failure of g4test_03MT. |
Let's see if this PR automatically triggers the bulid and run test. This is the first such test on a non-master branch.