-
Notifications
You must be signed in to change notification settings - Fork 123
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
Use latest version of Github actions for CI #399
Conversation
@@ -45,5 +45,5 @@ jobs: | |||
run: | | |||
cd main | |||
cd build | |||
ctest -C Debug --output-on-failure -V |
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.
The -V
flag I find is important, because if a test fails there will generally be some output that is useful.
It looks like we should be able to set it as an input, so that we can turn it on if required: https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions
Doesn't the --output-on-failure do exactly that? |
It's been a while, but I thought it didn't do that at all. There are often multiple sub-tests for each main test, so sometimes it's one of those sub-tests that fails. |
I improved that diagnostic somewhat in 7ae2e64. Would defining LOG4CXX_DEBUG=true in the CI workflows be helpful? |
It looks like this will be fine as-is. Sample output when a test fails:
|
According to this link actions/upload-artifact@v3 is scheduled for deprecation on November 30, 2024.
Also, reduce the volume of unit test output.