Skip to content

Fix check-pr-labels#11862

Merged
mergify[bot] merged 4 commits into
haskell:masterfrom
hasufell:CI-fix-check-pr-labels
May 24, 2026
Merged

Fix check-pr-labels#11862
mergify[bot] merged 4 commits into
haskell:masterfrom
hasufell:CI-fix-check-pr-labels

Conversation

@hasufell
Copy link
Copy Markdown
Member

@hasufell hasufell commented May 22, 2026 •
edited by ulysses4ever
Loading

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@hasufell hasufell requested a review from ulysses4ever May 22, 2026 15:25
@hasufell
Copy link
Copy Markdown
Member Author

hasufell commented May 22, 2026

short-circuits on PR creation: https://github.com/haskell/cabal/actions/runs/26296407588/job/77410085858?pr=11862

@hasufell
Copy link
Copy Markdown
Member Author

hasufell commented May 22, 2026

re-runs when label is added: https://github.com/haskell/cabal/actions/runs/26296576116/job/77410680351?pr=11862

ulysses4ever
ulysses4ever approved these changes May 22, 2026
View reviewed changes
Copy link
Copy Markdown
Collaborator

@ulysses4ever ulysses4ever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@ulysses4ever ulysses4ever added the merge me Tell Mergify Bot to merge label May 22, 2026
@hasufell
Copy link
Copy Markdown
Member Author

hasufell commented May 22, 2026

on i386 alex segfaults... I'm not sure it makes sense to invest time in this

@ulysses4ever
Copy link
Copy Markdown
Collaborator

ulysses4ever commented May 22, 2026

Perhaps not here: It'd be great to have the fixed label check in regardless of failures. Since these jobs aren't required (I hope), this should be merged normally (again, I hope).

@mergify mergify Bot added the ready and waiting Mergify is waiting out the cooldown period label May 22, 2026
@philderbeast
Copy link
Copy Markdown
Collaborator

philderbeast commented May 23, 2026 •
edited
Loading

Can we speed up the merge?
All other requests are falling
-- @zlonast on Cabal and Hackage matrix channel

Is this pull request one we want to add the merge delay passed label to?

@ulysses4ever
Copy link
Copy Markdown
Collaborator

ulysses4ever commented May 23, 2026

@philderbeast these days it's adviced to use "priority: high" for this purpose. I'll put it on.

@mergify mergify Bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels May 23, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 23, 2026 •
edited
Loading

Merge Queue Status

This pull request spent 1 hour 38 minutes 8 seconds in the queue, including 1 hour 27 minutes running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
All conditions
  • 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

Reason

The merge conditions cannot be satisfied due to failing checks

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 Bot added a commit that referenced this pull request May 23, 2026
@mergify
Merge of #11862
fb46122
@mergify mergify Bot mentioned this pull request May 23, 2026
Closed
86 tasks
@mergify mergify Bot added dequeued and removed queued labels May 23, 2026
@zlonast
Copy link
Copy Markdown
Collaborator

zlonast commented May 23, 2026

Problem with internet connection?

https://github.com/haskell/cabal/actions/runs/26333806091/job/77524104409

@zlonast zlonast added queued and removed dequeued labels May 23, 2026
@mergify mergify Bot added dequeued and removed queued labels May 23, 2026
@ulysses4ever
Copy link
Copy Markdown
Collaborator

ulysses4ever commented May 23, 2026

@mergify enqueue

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 23, 2026

enqueue

❌ Sorry but I didn't understand the command. Please consult the commands documentation 📚.

@ulysses4ever
Copy link
Copy Markdown
Collaborator

ulysses4ever commented May 23, 2026

@mergify queue

@zlonast
Copy link
Copy Markdown
Collaborator

zlonast commented May 24, 2026

@mergify queue

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026 •
edited
Loading

Merge Queue Status

This pull request spent 1 hour 32 minutes 45 seconds in the queue, including 1 hour 21 minutes 47 seconds running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
All conditions
  • 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

Reason

The merge conditions cannot be satisfied due to failing checks

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 May 24, 2026
mergify Bot added a commit that referenced this pull request May 24, 2026
@mergify
Merge of #11862
c95f0ba
@mergify mergify Bot mentioned this pull request May 24, 2026
Closed
86 tasks
@mergify mergify Bot added dequeued and removed queued labels May 24, 2026
@zlonast
Copy link
Copy Markdown
Collaborator

zlonast commented May 24, 2026

-----BEGIN CABAL OUTPUT-----
Error: cabal: '/usr/bin/curl' exited with an error:
curl: (6) Could not resolve host: hackage.haskell.org
-----END CABAL OUTPUT-----

@zlonast
Copy link
Copy Markdown
Collaborator

zlonast commented May 24, 2026

@mergify queue

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026 •
edited
Loading

Merge Queue Status

This pull request spent 1 hour 34 minutes 50 seconds in the queue, including 1 hour 23 minutes 45 seconds running CI.

Waiting for any of
  • check-neutral = Validate post job
  • check-skipped = Validate post job
  • check-success = Validate post job
All conditions
  • 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

Reason

The merge conditions cannot be satisfied due to failing checks

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 the queued label May 24, 2026
This was referenced May 24, 2026
Merged
Closed
mergify Bot added a commit that referenced this pull request May 24, 2026
@mergify
Merge of #11862
f57d00b
@mergify mergify Bot removed the dequeued label May 24, 2026
mergify Bot added a commit that referenced this pull request May 24, 2026
@mergify
Merge of #11862
ea02f1a
@mergify mergify Bot mentioned this pull request May 24, 2026
Closed
86 tasks
@mergify mergify Bot added dequeued and removed queued labels May 24, 2026
@zlonast
Copy link
Copy Markdown
Collaborator

zlonast commented May 24, 2026

https://github.com/haskell/cabal/actions/runs/26366106756/job/77610063612

Validate windows-latest ghc-9.6.7

        remove non-match subdir:                                                  OK (0.03s)
        invariant sorted 1:                                                       FAIL
          Exception: .\file-status--24116: CreateDirectory "\\\\?\\D:\\a\\cabal\\cabal\\cabal-install\\file-status--24116": permission denied (Access is denied.)
          Use -p '/invariant sorted 1/' to rerun this test only.
        invariant sorted 2:                                                       OK (0.04s)

@Bodigrim
Copy link
Copy Markdown
Collaborator

Bodigrim commented May 24, 2026

Validate windows-latest ghc-9.6.7

This one will be hopefully fixed by #11872.

@hasufell
Copy link
Copy Markdown
Member Author

hasufell commented May 24, 2026

The marge bot looks like a waste of time. Why don't you merge things yourself?

@mergify mergify Bot added queued and removed dequeued labels May 24, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 24, 2026 •
edited
Loading

Merge Queue Status

  • ✅ Entered queue — 2026-05-24 19:42 UTC · Rule: default
  • ✅ Checks skipped · PR is already up-to-date
  • ✅ Merged — 2026-05-24 19:54 UTC · at d9b37b89bf51e27ffc99116b75df0b5d261c83df · merge

This pull request spent 11 minutes 37 seconds in the queue, including 4 seconds running CI.

Required conditions to merge
  • #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 = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • 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

@mergify mergify Bot merged commit 28fe856 into haskell:master May 24, 2026
96 of 98 checks passed
@mergify mergify Bot removed the queued label May 24, 2026
@ulysses4ever
Copy link
Copy Markdown
Collaborator

ulysses4ever commented May 25, 2026

Thanks for pushing on this everyone!

@zlonast you don't have to ping the bot with queue commands when there's a CI issue: just restarting the failing jobs is enough. As soon as all required jobs succeeded, the bot will happily merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@philderbeast philderbeast philderbeast approved these changes

@ulysses4ever ulysses4ever ulysses4ever approved these changes

Assignees

No one assigned

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge priority: high 🔥 ready and waiting Mergify is waiting out the cooldown period run release build

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@hasufell @ulysses4ever @philderbeast @zlonast @Bodigrim