Many EWS bots are failing with to reach amazon aws, with the error: curl: (6) Could not resolve host: s3-us-west-2.amazonaws.com https://ews-build.webkit.org/#/builders/9/builds/10556/steps/6/logs/stdio https://ews-build.webkit.org/#/builders/3/builds/10644 https://ews-build.webkit.org/#/builders/14/builds/5202 https://ews-build.webkit.org/#/builders/15/builds/5699 https://ews-build.webkit.org/#/builders/17/builds/4471
This issue seems to have started this morning (~3 hours ago). First noticed failure in: https://ews-build.webkit.org/#/builders/24/builds/2224
DNS service Looks ok. ews116:~ buildbot$ host s3-us-west-2.amazonaws.com s3-us-west-2.amazonaws.com has address 52.218.229.192
Amazon status dashboard is now updated with DNS resolution flakiness: https://status.aws.amazon.com Aakash is looking into whether switching to a different address will help.
Created attachment 381607 [details] Screenshot - Amazon DNS Resolution Error
The issues are intermittent, and due to DNS Resolution Errors on Amazon side. I have added a fallback option (to download build archive from build master) in https://bugs.webkit.org/show_bug.cgi?id=203263
As per https://status.aws.amazon.com: [RESOLVED] Intermittent DNS Resolution Errors Between 10:30 AM and 6:30 PM PDT, we experienced intermittent errors with resolution of some AWS DNS names. Beginning at 5:16 PM, a very small number of specific DNS names experienced a higher error rate. These issues have been resolved.
Created attachment 381652 [details] Screenshot - [RESOLVED] Intermittent DNS Resolution Errors