Skip to content
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

Closed
vik748 opened this issue Mar 28, 2025 · 5 comments · Fixed by #1204
Closed

Comments

@vik748
Copy link

vik748 commented Mar 28, 2025

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:

VERSION 0.8

build:
    FROM ubuntu

    ARG CPR_VERSION=1.10.5

    # Install package dependencies
    RUN apt-get -q update && apt-get -q install -y --no-install-recommends \
            libcurl4-openssl-dev \
            build-essential \
            cmake \
            libssl-dev \
        && apt-get clean && rm -rf /var/lib/apt/lists/*

    WORKDIR /
    GIT CLONE --branch $CPR_VERSION https://github.com/libcpr/cpr cpr
    WORKDIR /cpr

    RUN mkdir build \
        && cd build \
        && cmake -DCPR_USE_SYSTEM_CURL=ON -DCPR_ENABLE_SSL=ON -DCMAKE_BUILD_TYPE=Release .. \
        && cmake --build . --parallel 4 --config Release \
        && cmake --install . --config Release \
        && ldconfig

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

  • OS: Ubuntu
  • Version: 20.04
    See Earthly file above for specific details.
@COM8
Copy link
Member

COM8 commented Mar 29, 2025

@vik748 thanks for reporting. Interesting that this only happens with the ALL_SANITIZERS_AVAILABLE test...
Let me see if I can throw together a quick fix for that :)

@COM8
Copy link
Member

COM8 commented Mar 29, 2025

#1204 should fix it. Can you please confirm?

@vik748
Copy link
Author

vik748 commented Mar 30, 2025

@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.

@COM8
Copy link
Member

COM8 commented Mar 30, 2025

Should not introduce any side effects. We just don't check for sanitizers any more if they are not enabled in the first place.

@vik748
Copy link
Author

vik748 commented Apr 14, 2025

@COM8 can we pls backport this fix into 1.10.x. We use influxdb which doesn't seem to build with 1.11.x on Ubuntu 20.04. Started #1208

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants