[AIRFLOW-6641] Better diagnostics for kubernetes flaky tests #7261
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
Kubernetes tests are sometimes flaky - they do not reach desired state and we do not know why. We need to make it less flaky and have enough diagnostics to understand what's going on.
Codecov Report
@@ Coverage Diff @@
## master #7261 +/- ##
===========================================
+ Coverage 32.96% 85.05% +52.09%
===========================================
Files 791 791
Lines 40137 40137
===========================================
+ Hits 13231 34139 +20908
+ Misses 26906 5998 -20908
Continue to review full report at Codecov.
|
mik-laj
reviewed
Jan 25, 2020
mik-laj
approved these changes
Jan 25, 2020
potiuk
added a commit
that referenced
this pull request
Jan 26, 2020
Kubernetes tests are sometimes flaky - they do not reach desired state and we do not know why. We need to make it less flaky and have enough diagnostics to understand what's going on. (cherry picked from commit 4e7bb5f)
kaxil
pushed a commit
that referenced
this pull request
Jan 26, 2020
Kubernetes tests are sometimes flaky - they do not reach desired state and we do not know why. We need to make it less flaky and have enough diagnostics to understand what's going on. (cherry picked from commit 4e7bb5f)
kaxil
pushed a commit
that referenced
this pull request
Feb 3, 2020
Kubernetes tests are sometimes flaky - they do not reach desired state and we do not know why. We need to make it less flaky and have enough diagnostics to understand what's going on. (cherry picked from commit 4e7bb5f)
galuszkak
pushed a commit
to FlyrInc/apache-airflow
that referenced
this pull request
Mar 5, 2020
…7261) Kubernetes tests are sometimes flaky - they do not reach desired state and we do not know why. We need to make it less flaky and have enough diagnostics to understand what's going on.
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.
Kubernetes tests are sometimes flaky - they do not reach desired state and we
do not know why. We need to make it less flaky and have enough diagnostics to
understand what's going on.
Issue link: AIRFLOW-6641
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX].In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.