upkeep: updated data set for 4.12 #27420
Conversation
|
/assign @dgoodwin |
|
I've filed https://issues.redhat.com/browse/TRT-553 to try to figure out what we do about Azure. File was last updated Aug 18, I can't explain why it looks so much worse now, it looks consistently terrible. 4.11 exhibits the same symptom even further back. I don't see a regression in the graphs but it's nearly impossible to tell with them in their current state. https://issues.redhat.com/browse/TRT-552 to get that addressed. The etcdGRPCRequestsSlow will help with a lot of job failures and we have a card already tracking this work. /lgtm |
|
/approve |
|
/retest-required |
openshift-ci
bot
added
the
approved
|
Worth noting the disruption values for most backends are likely double the real value, which is being fixed in #27415. I also need this to merge before that can to pickup the new cache backend data on single node. |
Signed-off-by: ehila <ehila@redhat.com>
eggfoobar
force-pushed
the
synthetictest_data_update
branch
from
8277cfc
to
2e7b965
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgoodwin, eggfoobar, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
We're just updating some json |
|
@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-aws-ovn-fips, ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-upgrade In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@eggfoobar: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@eggfoobar We discovered yesterday that some of the problems are massively influenced by single Topology, and ha isn't growing nearly like that, which doesn't seem to be in your chart. Is that being considered in your code to generate? |
|
@dgoodwin Good point! I just added the topology to the table being printed and this is what it shows up as now disruptions comparisons were above allowed leeway of
|
alerts comparisons were above allowed leeway of
1m0sdisruptions comparisons were above allowed leeway of
1m0sSigned-off-by: ehila ehila@redhat.com