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
[release-4.13] OCPBUGS-22099: Extend remote write test timeout #2127
[release-4.13] OCPBUGS-22099: Extend remote write test timeout #2127
Conversation
Problem: This test is increasingly flaky and blocks PR merges. It seems like the timeout is a bit too short for the configuration to propagate and metrics to be received at the remote write receiver. Solution: Extend timeout to 6 minutes. Issue: https://issues.redhat.com/browse/OCPBUGS-13939 Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
This commit attempts to improve the remote-write test. The queries to confirm things are working are simplified and the test message in case of failure will print the expected value and what was found. Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
@openshift-cherrypick-robot: Jira Issue OCPBUGS-13939 has been cloned as Jira Issue OCPBUGS-22099. Will retitle bug to link to clone. 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. |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-22099, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. 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. |
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.
/lgtm
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.
/lgtm
/label backport-risk-assessed |
/label cherry-pick-approved |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-22099, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/test e2e-agnostic-operator |
/lgtm let's see if this improves the test's flakyness! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielmellado, openshift-cherrypick-robot, simonpasquier, slashpai 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 |
/retest |
/test e2e-agnostic-operator |
1 similar comment
/test e2e-agnostic-operator |
@openshift-cherrypick-robot: all tests passed! 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. |
@openshift-cherrypick-robot: Jira Issue OCPBUGS-22099: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-22099 has been moved to the MODIFIED state. 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. |
This is an automated cherry-pick of #1971
/assign jan--f