-
Notifications
You must be signed in to change notification settings - Fork 973
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
Builds get stuck and fail in github workflow at "Performing Test ALL_SANITIZERS_AVAILABLE" #1203
Comments
@vik748 thanks for reporting. Interesting that this only happens with the |
#1204 should fix it. Can you please confirm? |
@COM8 thanks for the prompt action. So looks like the Sanitizer tests are being turned off by default. It certainly resolves my issues. Hopefully, it doesn't have undesired side-effects for others. |
Should not introduce any side effects. We just don't check for sanitizers any more if they are not enabled in the first place. |
Description
During CI/CD the build gets stuck at "Performing Test ALL_SANITIZERS_AVAILABLE".
Our CI/CD uses earthly and runs as a github workflow on a self-hosted runner on Amazon EC2. Every so often the
cmake ..
step get stuck at "Performing Test ALL_SANITIZERS_AVAILABLE" and eventually fails the job.I see a related problem mentioned in #582. I tried skipping the sanitizer tests completely by setting the flag "-DCMAKE_CROSSCOMPILING=ON" but this doesn't work since I believe CMAKE_CROSSCOMPILING is an internal cmake flag which is automatically set.
Example/How to Reproduce
Example Earthfile used in the workflow:
Possible Fix
Add a flag which can explicitly turn off the sanitizer tests.
Where did you get it from?
GitHub (branch e.g. master)
Additional Context/Your Environment
See Earthly file above for specific details.
The text was updated successfully, but these errors were encountered: