Chad Kimes
Chad Kimes
Let's keep it open, since the MacOS issue is still ongoing.
Thanks for generating the data @cpq! I investigated the runs from backend telemetry and I have found a pretty clear correlation with which datacenters the jobs are running on. I'm...
An update: it actually seems that only `time.windows.com` works for this particular DC. Other servers like `time.nist.gov` or `clock.isc.org` work from my home computer but not from MacOS in that...
Update: I'm still waiting on investigation from the network team.
I got confirmation that there is a network ACL blocking port 123 that is unexpectedly being applied to our traffic. I'm still working with the network team on a path...
The network team will be working on a change to isolate Mac traffic from this network rule. Not clear on rollout date, but I will update when I hear about...
Some of the timeouts in the logs appear to be HTTP related, e.g.: ``` Client.Timeout exceeded while awaiting headers ``` However others do look to be TCP timeouts. From one...
How many new processes are you creating during your testing? Connections will get reused within the scope of an existing process (and HTTP Client or Transport instance), but those connections...
A very crude and likely undesirable solution is to put a few minutes delay between steps that are heavy on connection usage, or organize the test order such that steps...
> An alternative approach I am considering is to create a tunnel to the K8s cluster. This way the Actions runner would have only one (persistent) connection to the cluster...