Skip to content

merge queue: embarking master (3fafd1e) and #11496 together - #11540

Closed
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/3bff4e3c38
Closed

merge queue: embarking master (3fafd1e) and #11496 together#11540
mergify[bot] wants to merge 2 commits into
masterfrom
mergify/merge-queue/3bff4e3c38

Conversation

@mergify

@mergify mergify Bot commented Feb 28, 2026

Copy link
Copy Markdown
Contributor

✨ The merge conditions cannot be satisfied due to failing checks. ✨

Branch master (3fafd1e) and #11496 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11496.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Required conditions to stay in the queue:

---
checking_base_sha: 3fafd1e688c3a34b877e8d6e22a9f00f3a0af5c7
previous_failed_batches: []
pull_requests:
  - number: 11496
...

Bodigrim and others added 2 commits February 24, 2026 20:33
…tems

There was time long ago when different file systems clocked file modification
time with significant granularity and `calibrateMtimeChangeDelay` had its purpose.
But this time is long gone and for the past decade all modern file systems
(ext4, ntfs, apfs) have submicrosecond granularity.

`calibrateMtimeChangeDelay` was used only in test suites and returned
values between 10ms and 1s. We can safely default it to 10ms, because
all modern file systems have finer precision. It's a low risk change:
after all it's only for tests, not for Cabal itself.

(Interestingly, it seems `calibrateMtimeChangeDelay` was never really fit for purpose:
its output is capped with 1s, while granularity of FAT filesystem is 2s)

As an extra precaution, modification time delay remains configurable
in the test suite via `--mtime-change-delay`.
@mergify mergify Bot closed this Feb 28, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/3bff4e3c38 branch February 28, 2026 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant