-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
libgcc_s.so.1 must be installed for pthread_cancel to work
during SCT's post-install validation
#3511
Comments
Thanks for bringing this to our attention! It looks like this is affecting SCT's main test suite, too. Notably, only some GitHub Actions CI runners are affected, though: Debian 9, Debian 10, Ubuntu 18.04, and CentOS 7. This also looks likes a recent change, as SCT's recurring cron job was fine prior to today: https://github.com/spinalcordtoolbox/spinalcordtoolbox/actions Investigating further... |
libgcc_s.so.1 must be installed for pthread_cancel to work
during SCT's post-install validation
Diffing the install logs, I found that these were the changes to the installed packages. The biggest change I notice is an update from EDIT: Pinning |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Aha! Currently, in
This is the exact import order that was reported to cause this error in ContinuumIO/anaconda-issues#9190. So, I tried importing |
What I still don't understand:
Still, hopefully this provides some new data points to help others reproduce the issue. |
Thanks for the investigation @joshuacwnewton ! I hope your PR will fix the problem because our CI is currently not very useful... Let me know if you need any help with this matter. |
Description
When submitting our
Shimming-Toolbox
Pull Request to the CI, we get an error that seems to be related to the installation ofSCT
. These tests were passing a few days ago and we have not modified our PR since then, so it seems to come fromSCT
's end.This happens with this PR and this one.
The bug happens when testing under
Ubuntu-18.04 3.8
.See error output
Steps to Reproduce
Follow this link and hit the
Re-run jobs
button.Expected behavior:
All the tests should pass.
Actual behavior:
The
Ubuntu-18.04 3.8
test fails and cancels the execution of all the other tests.The text was updated successfully, but these errors were encountered: