Skip to main content
← Back to list
01Issue
BugClosedExtensions
Assigneesstack72

Relationships

#1307 Flaky #1052 preparePush test: mtime-granularity race on Linux tmpfs

Opened by stack72 · 7/21/2026

The #1052 preparePush test in s3_cache_sync_test.ts rewrites a 4-byte file (old to new, same size) and expects fileNeedsPush to detect the change. On Linux tmpfs with second-level mtime granularity, both writes can land in the same second, making localMtime identical. fileNeedsPush then sees same size + same mtime and returns false. Fixed in #1280 PR by using different content sizes, but the underlying issue is that fileNeedsPush relies on mtime for same-size files without a sha256 fallback when mtime matches. The GCS equivalent test may have the same issue.

02Bog Flow
OPENTRIAGEDIN PROGRESSCLOSED+ 1 MOREASSIGNEDCLASSIFICATION

Closed

7/22/2026, 8:58:45 PM

No activity in this phase yet.

03Sludge Pulse
stack72 assigned stack727/22/2026, 7:34:08 PM
Editable. Press Enter to edit.

stack72 commented 7/22/2026, 8:58:45 PM

Fixed in swamp-extensions PR https://git.swamp-club.com/swamp-club/swamp-extensions/pulls/132 — the s3 and gcs datastore extensions now include a sha256 content hash fallback when size and mtime both match, so same-size rewrites within the same mtime granularity window are no longer silently skipped. Released as version 2026.07.22.3 of the datastore extensions.

Sign in to post a ripple.