merge queue: checking main (b1867aa) and #2075 together - #2078
mergify[bot] wants to merge 2 commits into
Conversation
Build output/compile_memory_top10.json from metrics.build_profile.compile_memory_usage. Each commit keeps only its current top 10 files; a file that drops out is emitted as null so Plotly evicts that trace at that date.
|
Thanks @mergify[bot] for opening this PR! You can do multiple things directly here: Once the workflow completes a message will appear displaying informations related to the run. Also the PR gets automatically reviewed by gemini, you can: |
Workflow reportworkflow report corresponding to commit 4c90989 Pre-commit check reportPre-commit check: ✅ Test pipeline can run. Clang-tidy diff reportNo relevant changes found. You should now go back to your normal life and enjoy a hopefully sunny day while waiting for the review. Doxygen diff with
|
✨ Pull request #2075 has been dequeued by @tdavidcl with a
dequeuecommand. ✨Branch main (b1867aa) and #2075 are queued together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #2075.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Bisected from a failed batch:
Required conditions of queue rule
main queuefor merge:check-success = allRequired conditions to stay in the queue:
approved-reviews-by >= 1check-success = all_lightcheck-success = pre-commit.ci - pr