Skip to content

merge queue: checking main (b1867aa) and #2075 together - #2078

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/2aa20bc90d
Closed

mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/2aa20bc90d

Conversation

@mergify

@mergify mergify Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

✨ Pull request #2075 has been dequeued by @tdavidcl with a dequeue command. ✨

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 queue for merge:

  • check-success = all

Required conditions to stay in the queue:

---
checking_base_sha: b1867aa3a14a0a85d925d916c8d5fad41c4c7d21
previous_check_retries: []
previous_failed_batches:
  - batch_pr_head_sha: ec773c4128f160bc20d33a7db02158c7591ec16a
    batch_pr_number: 2076
    checked_pull_requests:
      - 2075
      - 2049
    draft_pr_head_sha: ec773c4128f160bc20d33a7db02158c7591ec16a
    draft_pr_number: 2076
pull_requests:
  - number: 2075
    scopes: []
scopes: []
...

tdavidcl and others added 2 commits August 17, 2026 06:55
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.
@github-actions

Copy link
Copy Markdown
Contributor

Thanks @mergify[bot] for opening this PR!

You can do multiple things directly here:
1 - Comment pre-commit.ci run to run pre-commit checks.
2 - Comment pre-commit.ci autofix to apply fixes.
3 - Add label autofix.ci to fix authorship & pre-commit for every commit made.
4 - Add label light-ci to only trigger a reduced & faster version of the CI (need the full one before merge).
5 - Add label trigger-ci to create an empty commit to trigger the CI.

Once the workflow completes a message will appear displaying informations related to the run.

Also the PR gets automatically reviewed by gemini, you can:
1 - Comment /gemini review to trigger a review
2 - Comment /gemini summary for a summary
3 - Tag it using @gemini-code-assist either in the PR or in review comments on files

@mergify mergify Bot closed this Aug 17, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/2aa20bc90d branch August 17, 2026 11:09
@github-actions

Copy link
Copy Markdown
Contributor

Workflow report

workflow report corresponding to commit 4c90989
Commiter email is 37929162+mergify[bot]@users.noreply.github.com
You are using github private e-mail. This prevent proper tracing of who contributed what, please disable it (see Keep my email addresses private).

Pre-commit check report

Pre-commit check: ✅

trim trailing whitespace.................................................Passed
fix end of files.........................................................Passed
check for merge conflicts................................................Passed
check that executables have shebangs.....................................Passed
check that scripts with shebangs are executable..........................Passed
check for added large files..............................................Passed
check for case conflicts.................................................Passed
check for broken symlinks................................................Passed
check yaml...............................................................Passed
detect private key.......................................................Passed
No-tabs checker..........................................................Passed
Tabs remover.............................................................Passed
cmake-format.............................................................Passed
Validate GitHub Workflows................................................Passed
clang-format.............................................................Passed
ruff check...............................................................Passed
ruff format..............................................................Passed
Check doxygen headers....................................................Passed
Check license headers....................................................Passed
Check #pragma once.......................................................Passed
Check SYCL #include......................................................Passed
No ssh in git submodules remote..........................................Passed
No UTF-8 in files (except for authors)...................................Passed

Test pipeline can run.

Clang-tidy diff report

No relevant changes found.
Well done!

You should now go back to your normal life and enjoy a hopefully sunny day while waiting for the review.

Doxygen diff with main

Removed warnings : 0
New warnings : 0
Warnings count : 8182 → 8182 (0.0%)

Detailed changes :

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