TL/UCP: select exact allgather radix schedules

[jeffnvidia]

What

Add opt-in, message-size-aware exact-schedule selection for TL/UCP K-nomial
AllGather. This PR is stacked on the mixed-radix execution capability in #1327.

UCC_TL_UCP_ALLGATHER_KN_MIXED_RADICES has three states:

• unset or empty: preserve the legacy fixed-radix path;
• auto: select an exact fixed or mixed schedule;
• a list such as 8,6: use that authoritative exact schedule.

Policy

Automatic mode uses the total AllGather receive payload:

• below 1 GiB, enumerate exact factorizations from radices 2--9, minimize the
  number of phases, then minimize total fanout sum(radix - 1);
• at or above 1 GiB, retain the conservative R2-oriented exact factorization.

Ties use a deterministic priority order: powers of two first (8,4,2), then
the remaining radices in descending order. Uniform selected schedules are
normalized to the existing fixed-radix path. If no supported exact
factorization exists, selection falls back to the legacy path.

Examples:

Team	Message range	Schedule
60	small	4,5,3
64	small	fixed R8
72	small	8,9
96	small	4,4,6
128	small	8,4,4
96	large	2,2,2,2,2,3

Performance evidence

The legacy topology heuristic selects fixed R4 at 64 ranks and does not use
message size. The figures compare that measured execution path with current
auto and fixed R2/R4/R8. All values are out-of-place AllGather bus bandwidth.

Gaia: clear message-size crossover

At 64 ranks, current auto is execution-equivalent to measured explicit R8
below 1 GiB and explicit R2 from 1 GiB. It improves on legacy auto/R4 by
15.91% and 16.74% geometrically, respectively.

Doris: small-message gain and large-message convergence

A fresh 64-rank position-balanced run measured actual auto and explicit
R2/R4/R8 four times per size with 50 warmups and 100 timed iterations. Below
1 GiB, auto tracks R8 and improves on legacy auto/R4 by 5.60%
geometrically, with a 0.14% mean / 1.04% worst gap to the measured
candidate winner. At 1--8 GiB, R2/R4/R8 converge: auto is 0.10% above
legacy R4 and within 0.10% mean / 0.23% worst of the candidates. This is
non-regression evidence on Doris, not a meaningful R2 speedup.

Additional observations:

• Exact mixed schedules avoid the fixed-radix remainder penalty: at 96 ranks
  on Baby Lyris they reached about 96.4 GB/s at 8 GiB, versus 46--49 GB/s for
  fixed R2/R4/R8.
• For small messages, fewer phases consistently win. With phase count fixed,
  the exhaustive 72-rank Baby Lyris sweep ranked every permutation of the
  balanced 3,4,6 factors above the more uneven three-phase factorizations.
  At 32 ranks on Gaia, the balanced 2,4,4 family similarly beat 2,2,8.
• Ordering the same factor multiset was usually a secondary effect and showed
  no portable largest-first, largest-last, or PPN-first rule. The selector
  therefore uses a topology-independent cost and a stable ordering.
• Gaia and Baby Lyris favor R2 for large messages, while the crossover and the
  best schedule remain runtime- and platform-dependent. Explicit schedules
  remain available when a deployment has stronger local evidence.

Validation

• Selection tests cover an infeasible minimum phase count at 60 ranks, fixed
  R8, 8,6, 8,9, balanced 4,4,6 and 8,4,4, the large-message R2
  schedule, odd factors, and unsupported exact shapes.
• The preceding execution head passed a PyTorch-26.05 debug build,
  install/config validation, 9/9 focused tests, and CUDA AllGather checks on
  Gaia. Exact-head CI for the updated cost rule is pending.

[dpressle]

/build

[dpressle]

@ci-triage-agent

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — UCC%2Fucc-test-mpi · commit 2d72f80f

TL;DR: The ngc_pytorch build stage failed compiling allgather_knomial.c because PR #1328 calls ucc_array_size(candidates) — a function that doesn't exist in UCC — and -Werror turns the implicit-declaration warning into a hard error. Replace it with the existing UCX helper ucs_array_length() (or ucs_static_array_size()), whichever matches the candidates array type.

Full analysis

Summary: Build stage "Setup Image x86_64/ngc_pytorch/0" failed; make install aborted on a compile error in the TL/UCP allgather knomial component.

Root cause: src/components/tl/ucp/allgather/allgather_knomial.c:434 calls ucc_array_size(candidates), but no such symbol is declared anywhere (it's absent from ucc_math.h/ucc_datastruct.h; UCC uses UCX's ucs_array_* API). GCC emits -Werror=implicit-function-declaration (and -Werror=nested-externs), and because UCC is built with -Wall -Werror, the warning is fatal, killing the whole make -j16 install. This code path is new to PR #1328 (it does not exist on main), so it was never compiled before.

Implicated commit: [REDACTED:Hex High Entropy String] (the build under test), part of PR #1328 "TL/UCP: select exact allgather radix schedules". The touched file was last landed on main via e59b8083 (Sergey Lebedev, #1176), but the offending ucc_array_size call is added by #1328.

File: src/components/tl/ucp/allgather/allgather_knomial.c:434

Suggested fix: Replace ucc_array_size(candidates) with the correct array-length helper for however candidates is declared:

• If candidates is a UCX ucs_array_t, use ucs_array_length(candidates).
• If it's a plain C fixed-size array, use ucc_static_array_size(candidates) / ucs_static_array_size(candidates).

Then rebuild locally with -Werror to confirm the implicit-declaration and nested-externs warnings are gone. (Alternatively, if a ucc_array_size macro is genuinely intended, add it to src/utils/ucc_math.h, but reusing the existing UCX helper is preferred.)

Related: PR #1328 ; prior context PR #1176 (#1176).

🛡️ This comment had 1 potential secret(s) redacted (Hex High Entropy String). See request_id 7d992e62-d176-42e8-8c27-9d14379a7bc7 in the triage console for the audit trail.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 508e8d4e

TL;DR: The codestyle lint failed because commit TL/UCP: remove stale allgather radix initialization has a title 51 characters long, exceeding the 50-char limit; shorten that commit's title to ≤50 characters and force-push.

Full analysis

Summary: The "Lint (codestyle)" GitHub Actions job failed on its commit-title check — one commit title exceeds the 50-character maximum.

Root cause: The commit-title validator in .github/workflows/codestyle.yaml rejects any non-merge commit title longer than 50 characters (if [ ${#msg} -gt 50 ]). The commit titled TL/UCP: remove stale allgather radix initialization is 51 characters long, so check_title returned 1, setting ok=0 and exiting with code 1. The log shows: Commit title is too long: 51 / Bad commit title: 'TL/UCP: remove stale allgather radix initialization'. This is a lint policy failure, not a build/test error.

Implicated commit: The offending commit is the one titled TL/UCP: remove stale allgather radix initialization (part of PR #1328, branch jmahou/ucc-mixed-radix-selector). Exact SHA not shown in log; the PR HEAD is [REDACTED:Hex High Entropy String].

File: .github/workflows/codestyle.yaml (the check_title length check, [ ${#msg} -gt 50 ]) — the failure is in the commit message, not a source file.

Suggested fix: Reword that commit's title to ≤50 characters, e.g. TL/UCP: remove stale allgather radix init (41 chars) or TL/UCP: drop stale allgather radix init (39 chars). Rebase to amend the message (git rebase -i), then force-push the branch to re-run the check.

Related: none

🛡️ This comment had 1 potential secret(s) redacted (Hex High Entropy String). See request_id 582ac137-fce0-451d-8cb0-b9fcbc497836 in the triage console for the audit trail.

[jeffnvidia]

Maintainer note: this stacked PR inherits the intentional minimal tl_ucp.c
configuration entry from #1327. The selector-only diff remains unchanged at
294 additions / 17 deletions, and there are no formatter-suppression directives.

Any clang-format/codestyle complaint about the surrounding legacy configuration
table is the same issue described on #1327: formatting the one new entry expands
to the entire existing array. Please accept/waive the minimal form, or advise if
a separate formatting-only change is preferred.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit bf947bec

TL;DR: The codestyle "commit title" check failed because one commit title in PR #1328 exceeds the 50-character limit (it's 57 chars). Shorten that commit's title to ≤50 characters and force-push.

Full analysis

Summary: The codestyle job's commit-title lint step exited with code 1 because a commit message title is too long.

Root cause: The commit-title check enforces ${#msg} -gt 50 → fail (unless the title starts with Merge). The offending commit title TL/UCP: make automatic radix selection message-size aware is 57 characters, so the check printed Commit title is too long: 57 / Bad commit title and set ok=0, causing exit 1. This is a lint policy violation in the PR's commit history, not a code/build/test bug or a hang (the whole job ran in ~6 seconds with continuous output).

Implicated commit: The commit in PR #1328 (branch jmahou/ucc-mixed-radix-selector) titled TL/UCP: make automatic radix selection message-size aware (author: the PR author, jmahou). Note the checked-out HEAD is bf947bec "TL/UCP: simplify radix selector fallback", but the too-long title belongs to an earlier commit in the PR range.

File: .github/workflows/codestyle.yaml (the check_title function; the ${#msg} -gt 50 rule) — the fix is in git history, not this file.

Suggested fix: Reword the offending commit's title to ≤50 characters while keeping a valid header prefix (TL/UCP:). For example:

• TL/UCP: message-size aware radix selection (42 chars), or
• TL/UCP: size-aware auto radix selection (39 chars).

Use an interactive rebase to edit that commit, then force-push:

git rebase -i remotes/origin/<base>
# mark the "message-size aware" commit as 'reword', save a shorter title
git push --force-with-lease

All other titles passed, so no further changes are needed.

Related: none found.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit c968ff0d

TL;DR: The codestyle job's commit-title linter failed because one commit title exceeds the 50-character limit; shorten the title of the commit TL/UCP: make automatic radix selection message-size aware (57 chars) to ≤50 characters.

Full analysis

Summary: The "Run set -eE" commit-title check step in the codestyle workflow exited 1 because a PR commit title is longer than the allowed 50 characters.

Root cause: The linter's check_title() rejects titles longer than 50 chars (unless they start with Merge). The commit title TL/UCP: make automatic radix selection message-size aware is 57 characters, so the script printed Commit title is too long: 57 / Bad commit title, set ok=0, and exited with code 1. This is a lint policy violation, not an infrastructure/timeout issue — the whole job ran in ~8 seconds with continuous output.

Implicated commit: The PR commit titled TL/UCP: make automatic radix selection message-size aware (author: PR #1328 owner, jmahou). Full SHA not shown in log (only titles are printed by the linter).

File: .github/workflows/codestyle.yaml — the check_title() if [ ${#msg} -gt 50 ] rule (the offending data is the commit message itself, not a repo source file).

Suggested fix: Reword and amend the offending commit title to ≤50 characters, e.g. TL/UCP: message-size-aware radix selection (42 chars) or TL/UCP: size-aware auto radix selection (39 chars). Since this is one commit in a stacked series, use an interactive rebase (git rebase -i, mark that commit reword), then force-push the branch. No code change is required.

Related: PR #1328 (jmahou/ucc-mixed-radix-selector). No related issues found/searched — the diagnosis is fully determined by the log.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 4a8a3814

TL;DR: The codestyle lint job failed its commit-title-length check because one commit in PR #1328 has a 57-character title (limit is 50). Shorten that commit's title to ≤50 characters.

Full analysis

Summary: The codestyle job's commit-title validation step exited with code 1 after flagging one commit title as too long.

Root cause: The lint script rejects non-merge commit titles longer than 50 characters. The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters, producing Commit title is too long: 57 / Bad commit title and setting ok=0, which triggers exit 1. All other title checks passed (headers and format are fine); only length failed.

Implicated commit: The PR commit titled TL/UCP: make automatic radix selection message-size aware (author jmahou, branch jmahou/ucc-mixed-radix-selector). Full SHA not shown in log (only %h was printed); not the checked-out HEAD 4a8a3814.

File: .github/workflows/codestyle.yaml — the check_title() function, if [ ${#msg} -gt 50 ] length gate.

Suggested fix: Reword the offending commit title to ≤50 characters, e.g. TL/UCP: message-size-aware radix selection (42 chars) or TL/UCP: size-aware auto radix selection (39 chars), then rebase/force-push the branch (git rebase -i → reword that commit). No source-code change is needed; this is purely a commit-message policy violation.

Related: none

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit d75697ef

TL;DR: The codestyle lint failed because one commit title in PR #1328 exceeds the 50-character limit; shorten TL/UCP: make automatic radix selection message-size aware (57 chars) to ≤50 characters and force-push.

Full analysis

Summary: The codestyle GitHub Actions job failed its commit-title check because a non-merge commit title is longer than 50 characters.

Root cause: The check-title script in .github/workflows/codestyle.yaml rejects any non-Merge commit whose subject is longer than 50 characters. The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters, so check_title printed Commit title is too long: 57, set ok=0, and the script exited with code 1. All other titles in the branch passed.

Implicated commit: The offending commit is the one titled TL/UCP: make automatic radix selection message-size aware on branch jmahou/ucc-mixed-radix-selector (author jmahou; exact SHA not printed in the log — it uses %h short hashes that weren't echoed alongside titles). HEAD of the PR is [REDACTED:Hex High Entropy String].

File: .github/workflows/codestyle.yaml — the check_title() function, if [ ${#msg} -gt 50 ] guard.

Suggested fix: Reword that commit's subject to ≤50 characters and force-push the rebased branch. For example:

• TL/UCP: message-size aware auto radix (37 chars), or
• TL/UCP: size-aware auto radix selection (39 chars).

Use an interactive rebase (git rebase -i, mark the commit reword), then git push --force-with-lease. No source-code change is needed; this is purely a commit-message policy violation.

Related: none

🛡️ This comment had 1 potential secret(s) redacted (Hex High Entropy String). See request_id f938eab0-b0ff-4bfa-9c53-a8e7cb3af303 in the triage console for the audit trail.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit b75264f4

TL;DR: The codestyle job failed its commit-title lint because one commit in PR #1328 has a 57-character title, exceeding the 50-character limit; shorten that commit's title to ≤50 chars.

Full analysis

Summary: The "Lint (codestyle)" GitHub Actions job failed at the commit-title check step with exit code 1.

Root cause: The commit-title linter in .github/workflows/codestyle.yaml enforces a 50-character max on non-Merge commit titles. The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters long, so the check printed Commit title is too long: 57 / Bad commit title, set ok=0, and exited 1. All other commit titles passed. This is a lint policy violation, not a build/test hang — the job ran to completion in ~7 seconds.

Implicated commit: The commit with title TL/UCP: make automatic radix selection message-size aware (one of the commits in PR #1328 / branch jmahou/ucc-mixed-radix-selector; author not shown in log, likely jmahou). HEAD is [REDACTED:Hex High Entropy String].

File: .github/workflows/codestyle.yaml (the check_title/50-char length gate; msg length check if [ ${#msg} -gt 50 ])

Suggested fix: Reword that commit's title to 50 characters or fewer while keeping a valid TL/UCP: header, e.g.:

• TL/UCP: make auto radix message-size aware (43 chars), or
• TL/UCP: radix auto-select by message size (42 chars)

Apply via interactive rebase (git rebase -i, reword that commit) and force-push the branch. No source-code change is required; this is purely a commit-message policy failure.

Related: none

🛡️ This comment had 1 potential secret(s) redacted (Hex High Entropy String). See request_id bc6aa252-4165-4d2f-b2f9-77388b70d3f2 in the triage console for the audit trail.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 35531a8d

TL;DR: The codestyle job's commit-title linter failed because one commit title in PR #1328 exceeds the 50-character limit (57 chars); shorten that commit's subject line to ≤50 characters.

Full analysis

Summary: The codestyle GitHub Actions job's commit-title check exited with code 1 because a commit in the PR branch has a title longer than the allowed 50 characters.

Root cause: The check script in .github/workflows/codestyle.yaml enforces if [ ${#msg} -gt 50 ] for non-merge commit titles. The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters long, so the script printed Commit title is too long: 57 / Bad commit title, set ok=0, and exited 1. This is a lint policy violation, not a build/test failure or a timeout — the whole job ran in ~6 seconds with no gaps.

Implicated commit: The offending commit is the one titled TL/UCP: make automatic radix selection message-size aware (author: jmahou, branch jmahou/ucc-mixed-radix-selector). The tip commit checked out was 35531a8d "TL/UCP: make mixed-radix mode explicit".

File: .github/workflows/codestyle.yaml (the check_title function; length check if [ ${#msg} -gt 50 ]). The problem is in commit data, not the workflow file.

Suggested fix: Reword that commit's title to ≤50 characters and force-push. For example, interactively rebase (git rebase -i remotes/origin/<base>), mark that commit reword, and change the subject to something like TL/UCP: msg-size-aware auto radix (33 chars) or TL/UCP: size-aware auto radix selection (39 chars). All other commit titles in the range passed, so only that one needs editing.

Related: none

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 4f2877ce

TL;DR: The codestyle commit-title lint failed because one commit title exceeds the 50-character limit; shorten TL/UCP: make automatic radix selection message-size aware (57 chars) to ≤ 50 characters and force-push.

Full analysis

Summary: GitHub Actions Lint (codestyle) job failed at the commit-title check step with exit code 1.

Root cause: The codestyle workflow's check_title function rejects any commit title longer than 50 characters (unless it's a merge commit). The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters, triggering Commit title is too long: 57 → Bad commit title → ok=0 → exit 1. All other title/header/dot checks passed; this single overlong title is the only failure.

Implicated commit: The offending commit on branch jmahou/ucc-mixed-radix-selector titled TL/UCP: make automatic radix selection message-size aware (author not shown in log; part of PR #1328). The HEAD checked out was [REDACTED:Hex High Entropy String].

File: .github/workflows/codestyle.yaml (the set -eE / check_title step; the 50-char rule is at if [ ${#msg} -gt 50 ]).

Suggested fix: Reword the offending commit title to 50 characters or fewer while keeping a valid header prefix. For example, TL/UCP: message-size aware auto radix selection (47 chars) or TL/UCP: size-aware automatic radix selection (44 chars). Use an interactive rebase (git rebase -i, reword that commit) and force-push the branch. This is a genuine style violation, not an infra/flake issue — no workflow change needed.

Related: PR #1328 (openucx/ucc); no related issues found.

🛡️ This comment had 1 potential secret(s) redacted (Hex High Entropy String). See request_id bed25fdb-b001-4130-add9-ff36e89733c1 in the triage console for the audit trail.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 43a2ecf4

TL;DR: The codestyle lint job failed because one commit title in PR #1328 exceeds the 50-character limit; shorten it to pass. No code bug — it's a commit-message policy violation.

Full analysis

Summary: The "Lint (codestyle)" GitHub Actions job failed at the commit-title check step with exit code 1.

Root cause: The commit-title linter in .github/workflows/codestyle.yaml enforces a 50-character max on non-merge commit titles. The commit TL/UCP: make automatic radix selection message-size aware is 57 characters long, triggering Commit title is too long: 57 / Bad commit title, which sets ok=0 and exit 1. All other titles passed; this single title is the sole failure.

Implicated commit: The offending commit is the one titled TL/UCP: make automatic radix selection message-size aware on branch jmahou/ucc-mixed-radix-selector (PR #1328). (Short SHA not printed in this log; it's the 6th commit checked, between TL/UCP: simplify radix selector fallback and TL/UCP: simplify automatic radix selection.)

File: .github/workflows/codestyle.yaml — the check_title() function, guard if [ ${#msg} -gt 50 ].

Suggested fix: Reword that commit title to ≤ 50 characters (keeping a valid TL/UCP: header and no trailing period), then force-push. For example:

• TL/UCP: message-size aware auto radix (37 chars), or
• TL/UCP: size-aware auto radix selection (39 chars).
  Use an interactive rebase (git rebase -i, mark that commit reword) to edit only that title, then git push --force-with-lease. This is a policy check, not a source-code defect — no application file needs changing.

Related: none

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit f9edd8d4

TL;DR: The codestyle "Lint" job failed because one commit title in PR #1328 exceeds the 50-character limit; shorten TL/UCP: make automatic radix selection message-size aware (57 chars) to ≤50 characters.

Full analysis

Summary: The codestyle commit-title check failed — a commit title is longer than the allowed 50 characters.

Root cause: The workflow's check_title function rejects any non-Merge commit title longer than 50 characters. The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters, so the check printed Commit title is too long: 57 / Bad commit title, set ok=0, and exited with code 1. This is a lint policy violation, not a code or infrastructure error.

Implicated commit: The offending commit in PR #1328 (branch jmahou/ucc-mixed-radix-selector) with title TL/UCP: make automatic radix selection message-size aware. Author not shown in the log (only titles are printed); it is one of the PR's own commits.

File: .github/workflows/codestyle.yaml (the check_title logic, if [ ${#msg} -gt 50 ]) — the violation is in the commit message, not a source file.

Suggested fix: Reword the commit title to ≤50 characters and force-push. For example: TL/UCP: message-size aware auto radix (37) or TL/UCP: msg-size aware radix selection (38). Rebase interactively (git rebase -i), reword that commit, and push to re-trigger the check. All other 34 commit titles passed.

Related: none

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 56b71d77

TL;DR: The codestyle job failed because one commit title in PR #1328 is 57 characters — over the 50-char limit — and the fix is to reword/amend that commit title to ≤50 characters.

Full analysis

Summary: The codestyle commit-title lint step exited with code 1 because a commit title exceeded the 50-character maximum.

Root cause: The workflow's check_title() function rejects any non-Merge commit title longer than 50 characters. The commit titled 'TL/UCP: make automatic radix selection message-size aware' is 57 characters, triggering Commit title is too long: 57 → Bad commit title → ok=0 → exit 1. This is a genuine lint violation, not an infra flake (the whole job ran in ~2 seconds with no gaps/hangs).

Implicated commit: The offending commit in PR #1328 with title TL/UCP: make automatic radix selection message-size aware (author not shown in log; it's one of the branch jmahou/ucc-mixed-radix-selector commits). Head commit of the run is 56b71d77.

File: .github/workflows/codestyle.yaml — the check_title() if [ ${#msg} -gt 50 ] check (the rule); the actual defect is the commit message itself, not the source tree.

Suggested fix: Reword the offending commit title to ≤50 characters and force-push. For example:

• TL/UCP: make radix selection msg-size aware (44 chars), or
• TL/UCP: size-aware auto radix selection (39 chars).

Since this is mid-history in a large series, rebase interactively and reword that commit:

git rebase -i remotes/origin/<base>
# mark the "make automatic radix selection message-size aware" commit as `reword`
git push --force-with-lease

All other 36 titles passed, so only that one needs changing.

Related: none found.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 0ccdcff8

TL;DR: The codestyle job's commit-title linter failed because one commit title in PR #1328 exceeds the 50-character limit; shorten the offending commit title to ≤50 characters.

Full analysis

Summary: The codestyle GitHub Actions job failed at the commit-title check step (exit code 1) because a commit message title is too long.

Root cause: The CI script in codestyle.yaml enforces a 50-character maximum on non-merge commit titles. The commit title TL/UCP: make automatic radix selection message-size aware is 57 characters, so check_title returned 1 and set ok=0, causing exit 1. All other titles passed. This is a pure lint policy failure, not a build/test error:

Commit title is too long: 57
Bad commit title: 'TL/UCP: make automatic radix selection message-size aware'
##[error]Process completed with exit code 1.

Implicated commit: The commit in PR #1328 with title TL/UCP: make automatic radix selection message-size aware (author: jmahou, per branch jmahou/ucc-mixed-radix-selector). SHA not printed in this log; identify it via git log --oneline on the branch.

File: .github/workflows/codestyle.yaml (the check_title shell step; length check if [ ${#msg} -gt 50 ]).

Suggested fix: Reword that single commit title to 50 characters or fewer and force-push. For example: TL/UCP: message-size aware auto radix select (44 chars) or TL/UCP: size-aware auto radix selection (39 chars). Use interactive rebase (git rebase -i) to reword that commit, then git push --force-with-lease. No source-code change is needed.

Related: none

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 78b3ef46

TL;DR: The codestyle "commit title" check failed because one commit in PR #1328 has a 57-character title, exceeding the 50-char limit; shorten that commit's subject line to ≤50 chars and force-push.

Full analysis

Summary: The codestyle GitHub Actions job failed at the commit-title lint step (check_title) with exit code 1.

Root cause: The check enforces a maximum commit-title length of 50 characters (if [ ${#msg} -gt 50 ] in .github/workflows/codestyle.yaml). The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters long, so the script printed Commit title is too long: 57 / Bad commit title, set ok=0, and exited 1. Every other commit passed both the header-prefix and length checks — this single overlong title is the only violation.

Implicated commit: The offending commit is the one with subject TL/UCP: make automatic radix selection message-size aware on branch jmahou/ucc-mixed-radix-selector (author not shown in log; it is one of the PR #1328 commits, HEAD = [REDACTED:Hex High Entropy String]).

File: .github/workflows/codestyle.yaml (the check_title step, msg > 50 guard) — this is the check, not a bug; the fix is in the commit message itself.

Suggested fix: Rewrite the overlong commit title to ≤50 characters, e.g. TL/UCP: message-size-aware auto radix or TL/UCP: size-aware automatic radix select (both begin with an allowed TL/ header, contain no trailing dot). Use an interactive rebase to reword just that commit:

git rebase -i remotes/origin/<base>
# mark the "message-size aware" commit as "reword", shorten to <=50 chars
git push --force-with-lease

No source-code change is required; this is purely a commit-message policy violation.

Related: none found.

🛡️ This comment had 1 potential secret(s) redacted (Hex High Entropy String). See request_id d3c60724-8ecc-47cd-9ece-ed21225b30de in the triage console for the audit trail.

[svcnbu-swx-hpcx]

🤖 CI Triage Agent — Lint (codestyle) · commit 31eeeeb0

TL;DR: The Lint (codestyle) job failed because one commit title in PR #1328 exceeds the 50-character limit; shorten the offending commit message and the check will pass.

Full analysis

Summary: The commit-title lint step (.github/workflows/codestyle.yaml) exited 1 because a commit title is 57 characters, over the 50-char maximum.

Root cause: The codestyle check iterates over every commit in the PR range and enforces [ ${#msg} -gt 50 ]. The commit titled TL/UCP: make automatic radix selection message-size aware is 57 characters, so check_title returned 1 and set ok=0, causing the final exit 1. Every other title passed (correct header prefix, no trailing dot, ≤50 chars). This is purely a commit-message-length violation, not a code/build problem.

Implicated commit: The commit whose title is TL/UCP: make automatic radix selection message-size aware (in branch jmahou/ucc-mixed-radix-selector, PR #1328). Author not shown in log, but it is authored by the PR owner (jmahou).

File: .github/workflows/codestyle.yaml — the commit-title check (if [ ${#msg} -gt 50 ]); the violation is in the commit message itself, not in a source file.

Suggested fix: Reword that commit's title to ≤50 characters, e.g. TL/UCP: message-size-aware auto radix (37) or TL/UCP: size-aware automatic radix select (41). Since the branch has many commits, use an interactive rebase (git rebase -i, mark that commit reword), fix the title, then force-push. The lint will then pass.

Related: none found in logs.

Note: the log contains a redacted git basic-auth header (AUTHORIZATION: basic ***) emitted by actions/checkout — that's expected/masked, no action needed.