Skip to content

merge queue: checking main (79e0025) and #2083 together - #2086

Closed
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/6372d0ee19
Closed

merge queue: checking main (79e0025) and #2083 together#2086
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/6372d0ee19

Conversation

@mergify

@mergify mergify Bot commented Aug 17, 2026

Copy link
Copy Markdown

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

Branch main (79e0025) and #2083 are queued together for merge.

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

Required conditions of queue rule main queue for merge:

  • check-success = all

Required conditions to stay in the queue:

---
checking_base_sha: 79e0025793786a11fd0958dab784455e11772f6b
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 2083
    scopes: []
scopes: []
...

tdavidcl and others added 3 commits August 17, 2026 13:06
Build output/parse_time_top10.json from ClangBuildAnalyzer's
"Files that took longest to parse" section. 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.

Assisted-by: Cursor Grok 4.6
Keep both Plotly top-10 datasets: compile peak RSS from main and
parse time from this branch.

Assisted-by: Cursor Grok 4.6
@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 full-ci to run the full test suite (default is light CI; full CI also runs on Mergify merge-queue branches).
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

@github-actions

Copy link
Copy Markdown
Contributor

Workflow report

workflow report corresponding to commit 4c3a60d
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).
GitHub page artifact URL GitHub page artifact link (can expire)

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 : 8183 → 8183 (0.0%)

Detailed changes :

@mergify mergify Bot closed this Aug 18, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/6372d0ee19 branch August 18, 2026 00:09
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