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

What to do about "sometimes failing" tests? #3820

Open
GitMensch opened this issue Sep 11, 2024 · 0 comments
Open

What to do about "sometimes failing" tests? #3820

GitMensch opened this issue Sep 11, 2024 · 0 comments

Comments

@GitMensch
Copy link
Contributor

GitMensch commented Sep 11, 2024

In the last testruns I got the following tests failing but passing on rerun (sometimes the n-th time):

eventfd
async_signal_syscalls2-32
check_lost_interrupts
thread_stress
thread_stress-32
checkpoint_mmap_shared
condvar_stress-no-syscallbuf
mmap_adjacent_to_rr_usage
mutex_pi_stress
simple_threads_stress-32

I've got similar issues (also with other tests) before on several machines with different CPUs.
What I've recognized is that this is much more likely to happen when I run ctest with multiple jobs (more jobs, more likely).

Question: Should those failures just be ignored (and the wiki adjusted to always rerun the failed tests with a single job)?
If not: how to analyze this best?

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

No branches or pull requests

1 participant