Contact Details
No response
What happened?
I ran the launcher-based E2E test on my workstation (a MacBook Pro with Apple M2 Silicon) at the test case named "Same-Node Port Collision Creates New Launcher" crashed in a "kubectl wait" operation with a complaint about the client being "unable to decode an event from the watch stream". Initial investigation shows problems in the Kubernetes infrastructure.
Following is a typescript of the run.
fail727.log
Following are the two logs captured.
kas.log
kcm-p.log
Version
main (please specify commit below)
Branch name
MikeSpreitzer:scrape-populator
Commit SHA
94d9987
Relevant log output
Contact Details
No response
What happened?
I ran the launcher-based E2E test on my workstation (a MacBook Pro with Apple M2 Silicon) at the test case named "Same-Node Port Collision Creates New Launcher" crashed in a "kubectl wait" operation with a complaint about the client being "unable to decode an event from the watch stream". Initial investigation shows problems in the Kubernetes infrastructure.
Following is a typescript of the run.
fail727.log
Following are the two logs captured.
kas.log
kcm-p.log
Version
main (please specify commit below)
Branch name
MikeSpreitzer:scrape-populator
Commit SHA
94d9987
Relevant log output