[TEST] [WIP] Debug https_serving_main #15027
Closed
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
knative-prow
bot
added
area/test-and-release
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15027 +/- ##
==========================================
+ Coverage 84.11% 84.95% +0.83%
==========================================
Files 213 213
Lines 16783 13107 -3676
==========================================
- Hits 14117 11135 -2982
+ Misses 2315 1619 -696
- Partials 351 353 +2 ☔ View full report in Codecov by Sentry. |
|
/test ? |
|
@skonto: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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 https |
knative-prow
bot
added
size/S
|
/test https |
1 similar comment
|
/test https |
skonto
force-pushed
the
debug_https_serving_main
branch
from
c822b7c to
820b3b0
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: skonto 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 |
|
/test https |
Need to check why SLO fails as several requests fail. |
knative-prow
bot
added
size/M
|
/test https |
2 similar comments
|
/test https |
|
/test https |
skonto
changed the title
|
Looking at the logs dump: |
|
I managed to get some logs, so far I identified one container that was restarted, but that one was killed by the chaosduck: https://gist.github.com/ReToCode/f140c99b13ad9efe6d81b43344fb1824#file-logs-txt-L122 which seams reasonable. So we had these containers created (+) and deleted (-) that It seems like that pod is killed pretty often. Not sure if this should be the case or not with the chaosduck thing. Maybe @dprotaso knows more? But in general, that should not explain why we see errors on requests. |
|
I'd recommend disabling chaos duck for this component to see if it helps. If it does then create an issue to add some more resiliency after |
|
/retest |
skonto
force-pushed
the
debug_https_serving_main
branch
from
bc46b25 to
b5579cf
Compare
|
@skonto: The following tests failed, say
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. |
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.
Proposed Changes