-
Notifications
You must be signed in to change notification settings - Fork 37
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
Integration Test for proxy service propagation is flaky #874
Labels
bug
Something isn't working
jira
Issues that are synced to Jira
needs research
Further research is needed
testing
This issue adds or improves the testing
Milestone
Comments
engelmi
added
bug
Something isn't working
needs research
Further research is needed
testing
This issue adds or improves the testing
labels
Apr 10, 2024
Please assign me to this issue |
Merged
engelmi
added a commit
to engelmi/bluechi
that referenced
this issue
Sep 16, 2024
Relates to: eclipse-bluechi#874 The proxy service propagates failure integration test has been flaky due to a race condition where either the job of the requesting service gets canceled or the requesting service maps the inactive state due to the BindsTo=. In order to account for this race condition, lets check if either case occurred. Signed-off-by: Michael Engel <[email protected]>
engelmi
added a commit
to engelmi/bluechi
that referenced
this issue
Sep 16, 2024
Relates to: eclipse-bluechi#874 The proxy service propagates failure integration test has been flaky due to a race condition where either the job of the requesting service gets canceled or the requesting service maps the inactive state due to the BindsTo=. In order to account for this race condition, lets check if either case occurred. Signed-off-by: Michael Engel <[email protected]>
engelmi
added a commit
to engelmi/bluechi
that referenced
this issue
Sep 16, 2024
Relates to: eclipse-bluechi#874 The proxy service propagates failure integration test has been flaky due to a race condition where either the job of the requesting service gets canceled or the requesting service maps the inactive state due to the BindsTo=. In order to account for this race condition, lets check if either case occurred. Signed-off-by: Michael Engel <[email protected]>
engelmi
added a commit
to engelmi/bluechi
that referenced
this issue
Sep 16, 2024
Relates to: eclipse-bluechi#874 The proxy service propagates failure integration test has been flaky due to a race condition where either the job of the requesting service gets canceled or the requesting service maps the inactive state due to the BindsTo=. In order to account for this race condition, lets check if either case occurred. Signed-off-by: Michael Engel <[email protected]>
engelmi
added a commit
that referenced
this issue
Sep 17, 2024
Relates to: #874 The proxy service propagates failure integration test has been flaky due to a race condition where either the job of the requesting service gets canceled or the requesting service maps the inactive state due to the BindsTo=. In order to account for this race condition, lets check if either case occurred. Signed-off-by: Michael Engel <[email protected]>
Fixed in #943. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
jira
Issues that are synced to Jira
needs research
Further research is needed
testing
This issue adds or improves the testing
Describe the bug
The integration test
proxy-service-propagate-target-service-failure
is flaky.One of the most recent runs where it failed:
https://github.com/eclipse-bluechi/bluechi/actions/runs/8614446784
Since it seems to randomly fail, a more in-depth analysis is needed here.
To Reproduce
Not sure yet. A more in-depth analysis why the test fails (seemingly randomly) is needed.
Expected behavior
The test
proxy-service-propagate-target-service-failure
should always pass.The text was updated successfully, but these errors were encountered: