Skip to content

merge queue: checking main (8cdabf8) and #2047 together - #2052

Closed
mergify[bot] wants to merge 21 commits into
mainfrom
mergify/merge-queue/219e8c86d0
Closed

merge queue: checking main (8cdabf8) and #2047 together#2052
mergify[bot] wants to merge 21 commits into
mainfrom
mergify/merge-queue/219e8c86d0

Conversation

@mergify

@mergify mergify Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

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

Branch main (8cdabf8) and #2047 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #2047.
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: 8cdabf85d4db7c0ea0f674cb4c1153d3939f447a
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 2047
    scopes: []
scopes: []
...

tdavidcl and others added 21 commits August 13, 2026 16:37
Track Shamrock build times on debian-generic.acpp with -ftime-trace and
ClangBuildAnalyzer, without ccache or tests, on full CI runs.

Assisted-by: Composer
Co-authored-by: Cursor <cursoragent@cursor.com>
Rename the profile job, restore unrelated formatting, write ClangBuildAnalyzer.ini before analysis, and upload the report as an artifact.

Assisted-by: Cursor Grok 4.6
Parse the build profile report into metric__build_profile.json and
upload it as a workflow artifact.

Assisted-by: Cursor
Store the raw ClangBuildAnalyzer report text in {"data": ...} instead
of parsing it into a structured metric payload.

Assisted-by: Cursor
Add a reusable workflow that downloads all metric__* artifacts from the
current run, merges them into one JSON document with a UTC date and time,
and uploads the result. Call it after the main CI workflow on pull
requests and pushes.

Assisted-by: Cursor

Co-authored-by: timothee.davidcleris <timothee.davidcleris@proton.me>
Use clang_build_analyzer_report.txt so it is not picked up by the
on PR completed workflow report_* artifact filter.

Assisted-by: Cursor
Only add sha, ref, event_name, repository, workflow, run_id, and
run_attempt when the corresponding environment variable is not None,
so the same aggregator works on push and pull_request.

Assisted-by: Cursor

Co-authored-by: timothee.davidcleris <timothee.davidcleris@proton.me>
Assisted-by: Cursor

Co-authored-by: timothee.davidcleris <timothee.davidcleris@proton.me>
Assisted-by: Cursor

Co-authored-by: timothee.davidcleris <timothee.davidcleris@proton.me>
@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

@github-actions

Copy link
Copy Markdown
Contributor

Workflow report

workflow report corresponding to commit 0a368ea
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 : 8171 → 8171 (0.0%)

Detailed changes :

@mergify mergify Bot closed this Aug 14, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/219e8c86d0 branch August 14, 2026 21:35
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.

3 participants