Skip to content

merge queue: embarking master (802596a) and #11669 together#11880

Closed
mergify[bot] wants to merge 7 commits into
masterfrom
mergify/merge-queue/11bd832514
Closed

merge queue: embarking master (802596a) and #11669 together#11880
mergify[bot] wants to merge 7 commits into
masterfrom
mergify/merge-queue/11bd832514

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 24, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch master (802596a) and #11669 are embarked together for merge.

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

Required conditions of queue rule squash-merge for 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

Required conditions to stay in the queue:

---
checking_base_sha: 802596ae65e18fc9448ffb82bda5cefeec15c7de
previous_failed_batches: []
pull_requests:
  - number: 11669
    scopes: []
scopes: []
...

jappeace-sloth and others added 7 commits May 24, 2026 23:46
```
Error:
    The following packages are broken because other packages they depend on are missing. These broken packages must be rebuilt before they can be used.
planned package consumer-0.1.0.0 is broken due to missing package
  framework-0.1.0.0+95RTb42ZWxa9J13cUStM0q
````

To

```
Error:
    The following packages are broken because other packages they depend on are missing. These broken packages must be rebuilt before they can be used.
      planned package consumer-0.1.0.0
          is broken due to missing package
            framework-0.1.0.0 (has unfilled signature: App)
              The package is installed as indefinite.
              To use it, rebuild it in the same cabal project as the consumer so cabal can fill the signatures.
```

Hopefully it gives more guidence on what's going on to the user. I encountered this when trying to use backpack in a nix setup (for example jappeace-sloth/prrrrrrrrr#2) It keeps on wanting to build everything locally and I couldn't understand why. I still don't fully understand why it can't have partially filled modules upstream. It claims it's because of nix but I don't understand it.
Add missing expected output file for cabal variant of Backpack Fail5 test

The setupAndCabalTest function runs the test twice: once with setup and
once with cabal. The setup variant uses setup-external-fail.out, but the
cabal variant needs setup-external-fail.cabal.out which was missing,
causing the test to expect empty output and fail.
@mergify mergify Bot mentioned this pull request May 24, 2026
6 tasks
@mergify mergify Bot closed this May 25, 2026
@mergify mergify Bot deleted the mergify/merge-queue/11bd832514 branch May 25, 2026 00:23
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