[GH-ISSUE #2327] Investigate why `stat --cache=never` is necessary in integration tests. #1148

New issue

Open

opened 2026-03-04 01:51:44 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:51:44 +03:00

Owner

Originally created by @gaul on GitHub (Sep 23, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2327

CI recently started failing on CI runners despite no change to s3fs itself. We found that stat --cache=never works around this but it should not be necessary. Proposed workaround in #2319.

Originally created by @gaul on GitHub (Sep 23, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2327 CI recently started failing on CI runners despite no change to s3fs itself. We found that `stat --cache=never` works around this but it should not be necessary. Proposed workaround in #2319.

kerem commented

2026-03-04 01:51:45 +03:00

Author

Owner

@ggtakec commented on GitHub (Sep 24, 2023):

If the --cached option of the stat command is provided and that option is not specified on command line, it should behave as default.
The default setting is that it depends on the file system.
When this CI(Github Actions) started failing, I think there may have been a change in the volume options utilized by the Runner provided by Github.
It is a Runner that operates as a Container, and I think it may be affected by the settings on the host side setting.

I'm currently contacting Github support to find out if there were any changes made at that time.
(I've been waiting for the response for about a week now)

@ggtakec commented on GitHub (Sep 24, 2023): If the `--cached` option of the `stat` command is provided and that option is not specified on command line, it should behave as `default`. The `default` setting is that it depends on the file system. When this CI(Github Actions) started failing, I think there may have been a change in the volume options utilized by the Runner provided by Github. It is a Runner that operates as a Container, and I think it may be affected by the settings on the host side setting. I'm currently contacting Github support to find out if there were any changes made at that time. _(I've been waiting for the response for about a week now)_