Make integration test timeouts configurable #970
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/packit retest-failed |
2 similar comments
|
/packit retest-failed |
|
/packit retest-failed |
|
/packit retest-failed |
|
Tests on testing farm are currently pretty bittle... lets give it another try. |
|
/packit retest-failed |
1 similar comment
|
/packit retest-failed |
|
/packit test Note: Seems like the copr builds are not available, so triggering packit doesn't work (the linked run was from 3 days ago). I resigned the commit to trigger the full flow again. If it fails again only in TF because of some infra setup, lets merge still. |
engelmi
force-pushed
the
make-integration-test-timeouts-configurable
branch
from
9893d4c
to
6dc1687
Compare
engelmi
force-pushed
the
make-integration-test-timeouts-configurable
branch
3 times, most recently
from
d9d6f3a
to
72bd4b8
Compare
|
/packit retest-failed |
mkemel
approved these changes
Oct 28, 2024
|
/packit retest-failed |
Fixes: eclipse-bluechi#969 Depending on platforms, the default timeouts used in the integration tests need to be adjusted. In order to prevent code modification, lets have the three currently available, high-level timeouts be configurable via tmt. Signed-off-by: Michael Engel <[email protected]>
Fixes: eclipse-bluechi#971 Local provisioning is considered dangerous since tmt v1.38.0 and causes the pipeline to fail. In order to be able to run BlueChi integration tests, lets enable it by setting the environment variable TMT_FEELING_SAFE via --feeling-safe CLI option in the GitHub workflow and setting the env variable in packit. See: teemtee/tmt#3282 https://tmt.readthedocs.io/en/stable/overview.html#variables Signed-off-by: Michael Engel <[email protected]>
engelmi
force-pushed
the
make-integration-test-timeouts-configurable
branch
from
72bd4b8
to
447b339
Compare
|
/packit retest-failed |
|
Retriggered the pipeline again to see if the flaky tests are passing now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #969
Fixes: #971
Depending on platforms, the default timeouts used in the integration tests need to be adjusted. In order to prevent code modification, lets have the three currently available, high-level timeouts be configurable via tmt.
Local provisioning is considered dangerous since tmt v1.38.0 and causes the pipeline to fail. In order to be able to run BlueChi integration tests, lets enable it by setting the environment variable TMT_FEELING_SAFE via --feeling-safe CLI option in the GitHub workflow and via env variable in packit.
See:
teemtee/tmt#3282
https://tmt.readthedocs.io/en/stable/overview.html#variables