-
Notifications
You must be signed in to change notification settings - Fork 83
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
Minor bug fixes for the e2e test suite #2074
Merged
johscheuer
merged 3 commits into
FoundationDB:main
from
johscheuer:minor-bug-fixes-e2e-test-suite
Jun 24, 2024
Merged
Minor bug fixes for the e2e test suite #2074
johscheuer
merged 3 commits into
FoundationDB:main
from
johscheuer:minor-bug-fixes-e2e-test-suite
Jun 24, 2024
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
johscheuer
changed the title
Minor bug fixes for the e2e test suire
Minor bug fixes for the e2e test suite
Jun 21, 2024
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
johscheuer
commented
Jun 24, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Failures in the last run:
2024/06/21 17:02:58 reconciled name=fdb-cluster-v5i89er6, namespace=pr-947-rfdtai3c, generation:21
• [FAILED] [393.185 seconds]
Operator when a Pod is unscheduled and another Pod is being replaced [It] should remove the targeted Pod [e2e, pr]
/codebuild/output/src1254425878/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/test_operator/operator_test.go:583
[FAILED] Timed out after 300.001s.
Expected
<bool>: false
to be true
In [It] at: /codebuild/output/src1254425878/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/fixtures/fdb_cluster.go:1222 @ 06/21/24 17:02:16.558
------------------------------
and
• [FAILED] [785.261 seconds]
Operator Upgrades with chaos-mesh upgrading a cluster with link that drops some packets [It] Upgrade from 7.1.57 to 7.3.33 with network link that drops some packets [e2e, pr]
/codebuild/output/src1254425878/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/fixtures/upgrade_test_configuration.go:115
[FAILED] Unexpected error:
<*errors.errorString | 0x2902340>:
timed out waiting for the condition
{
s: "timed out waiting for the condition",
}
occurred
In [It] at: /codebuild/output/src1254425878/src/github.com/FoundationDB/fdb-kubernetes-operator/e2e/fixtures/fdb_cluster.go:1405 @ 06/21/24 16:54:42.427
------------------------------
johscheuer
commented
Jun 24, 2024
nicmorales9
approved these changes
Jun 24, 2024
Result of fdb-kubernetes-operator-pr on Linux CentOS 7
|
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.
Description
Fix a few minor bugs in the e2e test suite where some global variables were used instead of the factory scoped variables. This caused that some tests reused the same namespace and in some rare cases it could cause independent test suites to use the same namespace, which obviously caused conflicts.
Type of change
Please select one of the options below.
Discussion
Testing
Ran tests manually.
Documentation
Follow-up