amoeba commented on issue #40410:
URL: https://github.com/apache/arrow/issues/40410#issuecomment-1984541050
When running this test locally on my non-AMD64 Mac, I actually get three
failures:
```
[ RUN ] TestS3FS.CreateDir
/Users/bryce/src/apache/arrow/cpp/src/arrow/filesystem/s3fs_test.cc:934:
Failure
Failed
Expected 'fs_->CreateDir("bucket/somefile")' to fail with IOError, but got OK
[ FAILED ] TestS3FS.CreateDir (37 ms)
[ RUN ] TestS3FSGeneric.CopyFile
Warning: The standard parity is set to 0. This can lead to data loss.
/Users/bryce/src/apache/arrow/cpp/src/arrow/filesystem/test_util.cc:570:
Failure
Failed
Expected 'fs->CopyFile("AB/abc", "def/mno")' to fail with IOError, but got OK
[ FAILED ] TestS3FSGeneric.CopyFile (66 ms)
[ RUN ] TestS3FSGeneric.MoveFile
Warning: The standard parity is set to 0. This can lead to data loss.
/Users/bryce/src/apache/arrow/cpp/src/arrow/filesystem/test_util.cc:448:
Failure
Failed
Expected 'fs->Move("AB/pqr", "xxx/mno")' to fail with IOError, but got OK
[ FAILED ] TestS3FSGeneric.MoveFile (81 ms)
```
I see in this job we run ctest with,
```
ctest --label-regex unittest --output-on-failure --parallel 4 --repeat
until-pass:3 --timeout 300
```
My hunch is that it's possible the test is failing and ctest is retrying. My
local machine is fast enough that it can get 3 repeats in before the timeout
but it's possible GitHub's runner is slow enough that the timeout happens first.
Another thing I noticed is that, when ctest automatically re-attempts the
test as requested, it still prints "attempt 1/1" each time:
```
Running arrow-s3fs-test, redirecting output into
/Users/bryce/src/apache/arrow/cpp/build/build/test-logs/arrow-s3fs-test.txt
(attempt 1/1)
```
--
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]
