Skip to content

Backport #12246: Fix renameFileWithRetry leaving temporary files after copying - #12298

Merged
mergify[bot] merged 1 commit into
3.18from
mergify/bp/3.18/pr-12246
Sep 1, 2026
Merged

mergify[bot] merged 1 commit into
3.18from
mergify/bp/3.18/pr-12246

Conversation

@mergify

@mergify mergify Bot commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

@ffaf1 @TravisCardwell could you please check whether this fixes #12244?

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

@ffaf1

ffaf1 commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

Please, a moment of reflection before we merge this.
If we do, we are not releasing cabal-install only.

I am not saying that it is bad, I just want to have the consequences clear.

@ffaf1

ffaf1 commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

We have to release Cabal-syntax.

@ffaf1 ffaf1 added the merge me Tell Mergify Bot to merge label Aug 31, 2026
@mergify mergify Bot added the queued label Aug 31, 2026
@mergify

mergify Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

Merge Queue Status

  • Entered queue2026-08-31 13:51 UTC · Rule: default · triggered by rule Put backports in the rebase+merge queue
  • Checks failed · on draft merge queue: checking #12298 on 3.18 (4f8ce45) #12303
  • 🚫 Left the queue2026-08-31 14:05 UTC · at c696d8df315b7837265c2048c3f375dc59c54c1c

This pull request spent 13 minutes 50 seconds in the queue, including 2 minutes 34 seconds running CI.

Waiting for
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
    • check-success = Doctest Cabal
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Meta checks
    • check-skipped = Meta checks
    • check-success = Meta checks
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
    • check-success = Bootstrap post job
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
    • check-success = Check sdist post job
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
    • check-success = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Meta checks
    • check-skipped = Meta checks
    • check-success = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
    • check-success = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
    • check-success = Check sdist post job
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • 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 = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Reason

The merge conditions cannot be satisfied due to failing checks

  • docs/readthedocs.org:cabal
  • whitespace
  • Check sdist post job
  • Changelogs

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify Bot added dequeued and removed queued labels Aug 31, 2026
@zlonast

zlonast commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

@Mergifyio queue

@mergify

mergify Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Merge Queue Status

This pull request spent 19 minutes 8 seconds in the queue, including 8 minutes 36 seconds running CI.

Waiting for
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
    • check-success = Doctest Cabal
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • any of: [🛡 GitHub branch protection]
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
    • check-success = Bootstrap post job
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
    • check-success = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Validate post job
    • check-skipped = Validate post job
    • check-success = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
    • check-success = Bootstrap post job
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 GitHub branch protection]
  • 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 = 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

Reason

The merge conditions cannot be satisfied due to failing checks

  • Meta checks
  • docs/readthedocs.org:cabal
  • Bootstrap post job
  • whitespace
  • Check sdist post job
  • Changelogs

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify Bot added queued and removed dequeued labels Sep 1, 2026
@mergify mergify Bot added dequeued and removed queued labels Sep 1, 2026
@zlonast

zlonast commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Also #12307 (comment)

@zlonast zlonast added queued and removed dequeued labels Sep 1, 2026
@mergify mergify Bot added dequeued and removed queued labels Sep 1, 2026
@zlonast

zlonast commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

https://github.com/Mergifyio queue

@mergify

mergify Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Merge Queue Status

This pull request spent 2 hours 23 minutes 36 seconds in the queue, including 2 hours 11 minutes 37 seconds running CI.

Required conditions to merge
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • github-review-approved [🛡 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 = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • 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 = 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

@mergify mergify Bot added queued and removed dequeued labels Sep 1, 2026
@mergify
mergify Bot merged commit af0302b into 3.18 Sep 1, 2026
117 of 121 checks passed
@mergify
mergify Bot deleted the mergify/bp/3.18/pr-12246 branch September 1, 2026 14:31
@mergify mergify Bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days and removed queued labels Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants