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

Latest Ubuntu GitHub runner causes OpenMP tests to fail in CI #171

Closed
bryanpkc opened this issue Dec 29, 2023 · 0 comments · Fixed by #172
Closed

Latest Ubuntu GitHub runner causes OpenMP tests to fail in CI #171

bryanpkc opened this issue Dec 29, 2023 · 0 comments · Fixed by #172
Assignees

Comments

@bryanpkc
Copy link
Collaborator

From the CI job (https://github.com/flang-compiler/classic-flang-llvm-project/actions/runs/7309478286/job/19992674439) for PR #170:

Failed Tests (2):
  libomp :: affinity/kmp-affinity.c
  libomp :: affinity/omp-places.c

Even though there have been recent changes to the CI workflows, this particular job as specified in .github/workflows/llvm-project-tests.yml has not been updated. Comparing the failing run with a previous passing run (https://github.com/flang-compiler/classic-flang-llvm-project/actions/runs/6562896746/job/17825903837), it can be seen that both are using the ubuntu-latest runner (Ubuntu 22.04.3), and running the same commands to build and test the compiler.

One noticeable difference between the two is that the passing run had only two threads available (llvm-lit reported -- Testing: 66155 tests, 2 workers --), while the failing run had four threads on two cores. I suspect that the enablement of SMT on the runner, or the configuration of the Linux kernel on the runner, had somehow caused these tests to fail.

I propose to exclude these tests from the CI workflows for this repository.

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

Successfully merging a pull request may close this issue.

1 participant