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
NS race condition during test case #2494
Comments
Comment from firstyear (@Firstyear) at 2017-11-01 06:43:23 Metadata Update from @Firstyear:
|
Comment from mreynolds (@mreynolds389) at 2017-11-02 16:40:05 Metadata Update from @mreynolds389:
|
Comment from firstyear (@Firstyear) at 2017-11-06 00:33:55 |
Comment from firstyear (@Firstyear) at 2017-11-06 00:33:56 Metadata Update from @Firstyear:
|
Comment from mreynolds (@mreynolds389) at 2017-11-06 12:58:03 Metadata Update from @mreynolds389:
|
Comment from firstyear (@Firstyear) at 2017-11-06 23:14:40 commit 11974a0 |
Comment from firstyear (@Firstyear) at 2017-11-06 23:14:41 Metadata Update from @Firstyear:
|
Comment from mreynolds (@mreynolds389) at 2017-11-16 19:34:43 |
Comment from mreynolds (@mreynolds389) at 2017-11-16 19:34:44 Metadata Update from @mreynolds389:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49435
Issue Description
During the test case, a very very rare issue can be observed (maybe 1 in a million executions)
This appears to be a race between internal job rearm's state assertion, and the thread shutdown clearing the queues.
Note, this will not affect production releases, on our test builds.
The text was updated successfully, but these errors were encountered: