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

Flaky integration tests on Testing Farm #972

Open
engelmi opened this issue Oct 28, 2024 · 0 comments
Open

Flaky integration tests on Testing Farm #972

engelmi opened this issue Oct 28, 2024 · 0 comments
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

Comments

@engelmi
Copy link
Member

engelmi commented Oct 28, 2024

Describe the bug

Currently, a few tests are failing regularly on Testing Farm, making the runs quite flaky. Here are some examples, incl. a sample test run on Testing Farm:

  • bluechictl-is-enabled (see this run)
  • bluechi-heartbeat-node-disconnected (see this run)
  • bluechi-is-enabled (see this run)
  • bluechictl-monitor-unit-created-removed (see this run)

This needs more investigation why these tests fail sometimes.

Expected behavior

Tests should pass/fail consistently.

@engelmi engelmi added bug Something isn't working needs research Further research is needed testing This issue adds or improves the testing labels Oct 28, 2024
@mwperina mwperina added jira Issues that are synced to Jira and removed jira Issues that are synced to Jira labels Oct 31, 2024
mwperina added a commit to mwperina/bluechi that referenced this issue Nov 4, 2024
To improve performance of bluechictl-is-enabled test we will skip
checking existing unit file, if we already checked a unit with the same
enablement status before, when we traverse over list of all existing
unit files.

Relates: eclipse-bluechi#972
Signed-off-by: Martin Perina <mperina@redhat.com>
mwperina added a commit that referenced this issue Nov 5, 2024
To improve performance of bluechictl-is-enabled test we will skip
checking existing unit file, if we already checked a unit with the same
enablement status before, when we traverse over list of all existing
unit files.

Relates: #972
Signed-off-by: Martin Perina <mperina@redhat.com>
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
Projects
None yet
Development

No branches or pull requests

2 participants