bneradt opened a new pull request, #489: URL: https://github.com/apache/trafficserver-ci/pull/489
The shard labels were 0-based, so a three-shard run posted `URTest 0of3`, `1of3` and `2of3` and never `3of3`, which reads as an off-by-one. This labels the shards `1of3` through `3of3`. - `toplevel.pipeline` creates the shard labels and the skipped-tier contexts from 1, and the shard in an `[approve ci urtest N]` comment is now 1-based. - `urtest.pipeline` and the branch `autest.pipeline` convert the 1-based label back to the 0-based `SHARD` that `urtest.sh` and the AuTest slicing expect. - `branch_build.pipeline` labels the branch AuTest shards from 1 too, for consistency. The required status contexts change, so this needs to land together with the `.asf.yaml` update in apache/trafficserver (linked below). Until both are in, PRs will be missing one required URTest context. The ATSUnderground PR jobs (`GitHub-sec-master/GitHub-pr`, `autest-child`, `autest-toplevel`) are inline Jenkins scripts, so they were updated directly on the controller and already use the 1-based labels. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
