Skip to content

merge queue: checking master (ee7d5da), #12017, #12006 and [#11787 + #11769] together#12042

Closed
mergify[bot] wants to merge 8 commits into
masterfrom
mergify/merge-queue/17a8a26ec3
Closed

merge queue: checking master (ee7d5da), #12017, #12006 and [#11787 + #11769] together#12042
mergify[bot] wants to merge 8 commits into
masterfrom
mergify/merge-queue/17a8a26ec3

Conversation

@mergify

@mergify mergify Bot commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

🕵️ This combination of pull requests has failed checks. Mergify is waiting for other pull requests ahead in the queue to understand which one is responsible for the failure. 🕵️

Branch master (ee7d5da), #12017, #12006 and [#11787 + #11769] are queued together for merge.

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

Required conditions of queue rule 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]
  • #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: ab9c08c435fbbc7f090b23ff2567ffa23c0f83fb
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 11787
    scopes: []
  - number: 11769
    scopes: []
scopes: []
...

Bodigrim and others added 8 commits June 23, 2026 21:21
This new flag makes cabal-install dump timing information for the
various stages of building a package. This allows us to better see how
much time is spending in configure/build stages.
This commits adds two new fields of `BuildOptions`, namely `programPrefix`
and `programSuffix`. This allows the installed executable program prefix
and suffix to be set by `SetupHooks` for packages with `build-type: Hooks`.

Fixes #11168
@mergify mergify Bot closed this Jun 27, 2026
@mergify mergify Bot deleted the mergify/merge-queue/17a8a26ec3 branch June 27, 2026 20:42
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.

3 participants