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

Remove racey start condition for ping thread #4693

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

qkoziol
Copy link
Contributor

@qkoziol qkoziol commented Aug 3, 2024

No description provided.

@qkoziol
Copy link
Contributor Author

qkoziol commented Aug 3, 2024

@lrknox - I believe that this should address the intermittent failure for the semaphore test

Copy link
Collaborator

@lrknox lrknox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So far this seems to fix the tests that intermittently fail.

@lrknox lrknox added Merge - To 1.14 Priority - 1. High 🔼 These are important issues that should be resolved in the next release Component - Testing Code in test or testpar directories, GitHub workflows Type - Bug / Bugfix Please report security issues to [email protected] instead of creating an issue on GitHub labels Aug 5, 2024
@lrknox lrknox merged commit 6061296 into HDFGroup:develop Aug 5, 2024
60 checks passed
@lrknox
Copy link
Collaborator

lrknox commented Aug 6, 2024

@qkoziol this may have addressed the intermittent failure on the machines where it was first noticed, but there are still some on machines with newer compilers (gcc 10 & 12, clang 18 on ubuntu 24.04, oneapi 2023). It's too soon to say whether those are intermittent or fail consistently.

@qkoziol
Copy link
Contributor Author

qkoziol commented Aug 6, 2024

@qkoziol this may have addressed the intermittent failure on the machines where it was first noticed, but there are still some on machines with newer compilers (gcc 10 & 12, clang 18 on ubuntu 24.04, oneapi 2023). It's too soon to say whether those are intermittent or fail consistently.

OK, thanks for the update. Are those configurations in the CI action, so I could test against them?

@qkoziol qkoziol deleted the fix_semaphore_test branch August 6, 2024 19:07
@lrknox
Copy link
Collaborator

lrknox commented Aug 6, 2024

@qkoziol Autotools TestExpress Workflows / Autotools debug Express Test Workflows failed the ttsafe test in the action after I merged #4694. Can you try that one?

These links show the ttsafe test failures reported to the 2 CDash instances for 8/6:
https://my.cdash.org/testSummary.php?project=1850&name=H5TEST-ttsafe&date=2024-08-06
https://cdash.hdfgroup.org/testSummary.php?project=7&name=H5TEST-ttsafe&date=2024-08-06

Clang is the compiler most common in these failures, followed by Intel (oneAPI) and gcc 11,12,13.
The most common machine for the failures last week was ec2-centos8, with either gcc 8.5, IntelLLVM 2024.1.0, or clang 12.0.1: https://my.cdash.org/testSummary.php?project=1850&name=H5TEST-ttsafe&date=2024-08-02

You can find the compiler and configure command for the failed tests in the links above by clicking on "Failed", then on the build name link, and then on the "0" for configure errors.

@qkoziol
Copy link
Contributor Author

qkoziol commented Aug 17, 2024

@lrknox - I spent a while poking at this before I noticed that I was accessing a variable outside of the semaphore protection. This PR: #4725 should fix the problem.

@lrknox lrknox added Merge - Develop Only This cannot be merged to previous versions of HDF5 (file format or breaking API changes) and removed Merge - To 1.14 labels Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - Testing Code in test or testpar directories, GitHub workflows Merge - Develop Only This cannot be merged to previous versions of HDF5 (file format or breaking API changes) Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Bug / Bugfix Please report security issues to [email protected] instead of creating an issue on GitHub
Projects
Status: Needs Merged
Development

Successfully merging this pull request may close these issues.

3 participants