Hello,
Sometimes, I encountered unexpected network connection timed out and DNS resolution failure in Arm containers. These unexpected failures were a little bit annoying. Does anyone meet the same issues? Please see the build report below:
https://travis-ci.org/yzyuestc/ovs/jobs/627526473#L12835
https://travis-ci.org/yzyuestc/ovs/jobs/627526477#L431
It would be great if the Arm container is a little bit more stable. Any comments are appreciated.
Cheers
Plus: Because I ran jobs for x86 and Arm64 simultaneously, I found no such issues exist in amd64 vm. Please see: https://travis-ci.org/yzyuestc/ovs/builds/627526446
I’ve had these problems yesterday, but none of today’s arm64 builds failed because of network problems.
+1 - I’ve been seeing this for a week or so and they continue today
yesterday, failed on deploy connecting / DNS lookup to github - https://travis-ci.org/jay0lee/got-your-back/jobs/628514959?utm_medium=notification&utm_source=email
4 days ago, failed during test runs with an issue looking up www.googleapis.com - https://travis-ci.org/jay0lee/GAM/jobs/627370366?utm_medium=notification&utm_source=email
Today, I re-run some jobs on Travis CI.
The name resolution failure issue occurred again. Please see the report:
https://travis-ci.org/yzyuestc/ovs/jobs/629898871
Thanks for reporting on that one. We are investigating possible improvement on our end and will get back to you if successfully applied.
Hi @jay0lee @yzyuestc @s09bQ5
We’ve added some DNS related improvements yesterday (changelog to follow shortly). Could you let us know if you still run into name resolution failures on arm builds?
Hi Michal @Michal, The name resolution failed on Arm occurred again. Please refer to the report: https://travis-ci.org/github/yzyuestc/ovs/jobs/692495844#L624
I’ve seen similar issues many times, but also in regular x86_64 builds. They always go away after restarting a job, which makes it difficult to reproduce.