Skip to content

merge-queue: embarking main (6c0e749) and #4533 together#4565

Closed
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/main/4533
Closed

merge-queue: embarking main (6c0e749) and #4533 together#4565
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/main/4533

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jun 3, 2022

🙁 This combination of pull requests has failed checks. #4533 will be removed from the queue. 🙁

Branch main (6c0e749) and #4533 are embarked together for merge.

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

Required conditions of queue low for merge:

  • any of [🛡 GitHub branch protection]:
    • check-success=Test stable on ubuntu-latest
    • check-neutral=Test stable on ubuntu-latest
    • check-skipped=Test stable on ubuntu-latest
  • any of [🛡 GitHub branch protection]:
    • check-success=Test integration with lightwalletd
    • check-neutral=Test integration with lightwalletd
    • check-skipped=Test integration with lightwalletd
  • any of [🛡 GitHub branch protection]:
    • check-success=Clippy
    • check-neutral=Clippy
    • check-skipped=Clippy
  • any of [🛡 GitHub branch protection]:
    • check-success=Rustfmt
    • check-neutral=Rustfmt
    • check-skipped=Rustfmt
  • any of [🛡 GitHub branch protection]:
    • check-success=Test with fake activation heights
    • check-neutral=Test with fake activation heights
    • check-skipped=Test with fake activation heights
  • any of [🛡 GitHub branch protection]:
    • check-success=Test all
    • check-neutral=Test all
    • check-skipped=Test all
  • any of [🛡 GitHub branch protection]:
    • check-success=Test stable on macos-latest
    • check-neutral=Test stable on macos-latest
    • check-skipped=Test stable on macos-latest
  • any of [🛡 GitHub branch protection]:
    • check-success=Test stable zebra-state with fake activation heights on ubuntu-latest
    • check-neutral=Test stable zebra-state with fake activation heights on ubuntu-latest
    • check-skipped=Test stable zebra-state with fake activation heights on ubuntu-latest
  • any of [🛡 GitHub branch protection]:
    • check-success=mergefreeze
    • check-neutral=mergefreeze
    • check-skipped=mergefreeze
  • any of [🛡 GitHub branch protection]:
    • check-success=Check deny.toml bans
    • check-neutral=Check deny.toml bans
    • check-skipped=Check deny.toml bans
  • any of [🛡 GitHub branch protection]:
    • check-success=Check deny.toml sources
    • check-neutral=Check deny.toml sources
    • check-skipped=Check deny.toml sources
  • any of [🛡 GitHub branch protection]:
    • check-success=Check Cargo.lock is up to date
    • check-neutral=Check Cargo.lock is up to date
    • check-skipped=Check Cargo.lock is up to date
  • any of [🛡 GitHub branch protection]:
    • check-success=Build stable zebra-chain w/o features on ubuntu-latest
    • check-neutral=Build stable zebra-chain w/o features on ubuntu-latest
    • check-skipped=Build stable zebra-chain w/o features on ubuntu-latest
  • any of [🛡 GitHub branch protection]:
    • check-success=Find available cached state disks
    • check-neutral=Find available cached state disks
    • check-skipped=Find available cached state disks
  • any of [🛡 GitHub branch protection]:
    • check-success=Install zebrad from lockfile without cache on ubuntu-latest
    • check-neutral=Install zebrad from lockfile without cache on ubuntu-latest
    • check-skipped=Install zebrad from lockfile without cache on ubuntu-latest
  • any of [🛡 GitHub branch protection]:
    • check-success=Test checkpoint sync from empty state
    • check-neutral=Test checkpoint sync from empty state
    • check-skipped=Test checkpoint sync from empty state
  • any of [🛡 GitHub branch protection]:
    • check-success=Build / Build images
    • check-neutral=Build / Build images
    • check-skipped=Build / Build images
  • any of [🛡 GitHub branch protection]:
    • check-success=Zebra checkpoint update / Run sync-past-checkpoint test
    • check-neutral=Zebra checkpoint update / Run sync-past-checkpoint test
    • check-skipped=Zebra checkpoint update / Run sync-past-checkpoint test
  • any of [🛡 GitHub branch protection]:
    • check-success=Zebra tip JSON-RPC / Run fully-synced-rpc test
    • check-neutral=Zebra tip JSON-RPC / Run fully-synced-rpc test
    • check-skipped=Zebra tip JSON-RPC / Run fully-synced-rpc test
  • any of [🛡 GitHub branch protection]:
    • check-success=Zebra checkpoint / Run sync-to-checkpoint test
    • check-neutral=Zebra checkpoint / Run sync-to-checkpoint test
    • check-skipped=Zebra checkpoint / Run sync-to-checkpoint test
  • any of [🛡 GitHub branch protection]:
    • check-success=Zebra tip / Run full-sync-to-tip test
    • check-neutral=Zebra tip / Run full-sync-to-tip test
    • check-skipped=Zebra tip / Run full-sync-to-tip test
  • any of [🛡 GitHub branch protection]:
    • check-success=Coverage on stable
    • check-neutral=Coverage on stable
    • check-skipped=Coverage on stable
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • base=main

More informations about Mergify merge queue can be found in the documentation.

Mergify commands

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the queue rules

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

dependabot bot and others added 2 commits June 1, 2022 03:55
Bumps [hyper](https://github.com/hyperium/hyper) from 0.14.18 to 0.14.19.
- [Release notes](https://github.com/hyperium/hyper/releases)
- [Changelog](https://github.com/hyperium/hyper/blob/master/CHANGELOG.md)
- [Commits](hyperium/hyper@v0.14.18...v0.14.19)

---
updated-dependencies:
- dependency-name: hyper
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@mergify
Copy link
Contributor Author

mergify bot commented Jun 3, 2022

The pull request #4533 cannot be merged and has been disembarked

@mergify mergify bot closed this Jun 3, 2022
@mergify mergify bot deleted the mergify/merge-queue/main/4533 branch June 3, 2022 06:15
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.

0 participants