thisisnic opened a new issue, #48641:
URL: https://github.com/apache/arrow/issues/48641

   ### Describe the bug, including details regarding any error messages, 
version, and platform.
   
   Multiple R nightly builds are fialing with SSCache errors, e.g. 
https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=72201&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=6c939d89-0d1a-51f2-8b30-091a7a82e98c&l=900
   
   ```
   range: 0-
   
   Source:
      error sending request for url 
(https://s3.$(sccache_region).amazonaws.com/***/sccache/.sccache_check): client 
error (Connect): dns error: failed to lookup address information: Name does not 
resolve: failed to lookup address information: Name does not resolve
   
   Backtrace:
      0: <unknown>
      1: <unknown>
      2: <unknown>
      3: <unknown>
      4: <unknown>
      5: <unknown>
      6: <unknown>
      7: <unknown>
      8: <unknown>
      9: <unknown>
     10: <unknown>
     11: <unknown>
     12: <unknown>
     13: <unknown>
     14: <unknown>
   
   
   Run with SCCACHE_LOG=debug SCCACHE_NO_DAEMON=1 to get more information
   make[2]: *** [src/arrow/CMakeFiles/arrow_array.dir/build.make:76: 
src/arrow/CMakeFiles/arrow_array.dir/array/array_base.cc.o] Error 2
   make[1]: *** [CMakeFiles/Makefile2:744: 
src/arrow/CMakeFiles/arrow_array.dir/all] Error 2
   make[1]: *** Waiting for unfinished jobs....
   sccache: error: Server startup failed: cache storage failed to read: 
Unexpected (temporary) at read => send http request
   
   Context:
      url: https://s3.$(sccache_region).amazonaws.com/***/sccache/.sccache_check
      called: http_util::Client::send
      service: s3
      path: .sccache_check
      range: 0-
   ```
   
   ### Component(s)
   
   Continuous Integration


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to