-
Notifications
You must be signed in to change notification settings - Fork 32
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
Fix position check after propagating #1094
Fix position check after propagating #1094
Conversation
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.
Whoops, I guess the testing wouldn't "fail" but we'd just get a billion error messages 😂 sorry.
Do you think you (or I) could add a test for the error message? We could add one to the along-step test, use the scoped logger, and make a giant (km) cube of lead and start the particle far enough away and low enough energy that x + step == x
.
That sounds good, I can try to put together a test. |
@amandalund I reproduced locally the CI failure you're seeing:
Pretty easy fix; this is just to geant4 not doing cleanup correctly. We just have to add the correct |
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 and nice test!
Ahh, thanks for reproducing and fixing that failure @sethrj! |
Oops I think I needed to update the test to work with other unit systems... |
WTF, why did it merge with the checks unpassed... EDIT: grrr... https://emmer.dev/blog/skippable-github-status-checks-aren-t-really-required/ |
Also can you add else
{
EXPECT_TRUE(scoped_log_.empty()) << scoped_log_;
} to the |
Will do! |
Sorry, missed this in the review of #1090.