Skip to content

[Chore][CI]: Change dst for K3 nightly comprehensive results#2958

Merged
sammshen merged 1 commit intoLMCache:devfrom
sammshen:k3-change-nightly-dst
Apr 6, 2026
Merged

[Chore][CI]: Change dst for K3 nightly comprehensive results#2958
sammshen merged 1 commit intoLMCache:devfrom
sammshen:k3-change-nightly-dst

Conversation

@sammshen
Copy link
Copy Markdown
Contributor

@sammshen sammshen commented Apr 5, 2026

Allows a fine-grained PAT that never expires for the CI machine to push results to.

What this PR does / why we need it:

Special notes for your reviewers:

If applicable:

  • this PR contains user facing changes - docs added
  • this PR contains unit tests

Note

Medium Risk
Moderate risk: changes the checkout/push flow and destination repo for baseline artifacts, which could break nightly uploads if credentials/branch setup differ or cloning fails.

Overview
Nightly baseline upload now publishes rolling benchmarks/long_doc_qa artifacts to a dedicated repo (LMCache/LMCache-CI) on benchmarks-main instead of pushing back to the main LMCache repository.

The script replaces the prior origin/benchmarks-main fetch/worktree logic and dynamic push URL construction with a git clone of the CI repo (creating an orphan branch if missing) and pushes via origin with a normal/force-push fallback using GITHUB_TOKEN when available.

Reviewed by Cursor Bugbot for commit 0d63c99. Bugbot is set up for automated code reviews on this repo. Configure here.

The GitHub PAT for the main repo expired, causing nightly baseline
uploads to fail. Switch the upload target to the dedicated
LMCache/LMCache-CI repository instead of pushing to benchmarks-main
on the main LMCache repo.

Signed-off-by: Samuel Shen <slshen@uchciago.edu>
@sammshen sammshen requested a review from deng451e April 5, 2026 06:15
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the baseline upload script to push benchmark results to a dedicated CI repository (LMCache/LMCache-CI) instead of the main repository, including logic for GITHUB_TOKEN authentication. A review comment suggests removing stderr suppression during git push operations to improve debuggability of CI failures, as hiding error messages complicates troubleshooting and constitutes technical debt.

Comment on lines +119 to +121
if ! git push origin "HEAD:${CI_BRANCH}" 2>/dev/null; then
echo "[WARN] Normal push failed, force-pushing..."
git push "$PUSH_URL" +HEAD:benchmarks-main 2>/dev/null || {
echo "[ERROR] Failed to push baselines to benchmarks-main"
git push origin "+HEAD:${CI_BRANCH}" 2>/dev/null || {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Suppressing stderr with 2>/dev/null during git push makes it difficult to diagnose failures in CI. If the push fails due to authentication issues (e.g., an expired or insufficient PAT), permission errors, or network problems, the actual error message will be hidden, leaving only the generic error message. Removing the redirection allows for better debuggability of CI failures.

Suggested change
if ! git push origin "HEAD:${CI_BRANCH}" 2>/dev/null; then
echo "[WARN] Normal push failed, force-pushing..."
git push "$PUSH_URL" +HEAD:benchmarks-main 2>/dev/null || {
echo "[ERROR] Failed to push baselines to benchmarks-main"
git push origin "+HEAD:${CI_BRANCH}" 2>/dev/null || {
if ! git push origin "HEAD:${CI_BRANCH}"; then
echo "[WARN] Normal push failed, force-pushing..."
git push origin "+HEAD:${CI_BRANCH}" || {
References
  1. The style guide emphasizes focusing on technical debt and future maintainability. Hiding error messages in CI scripts is a form of technical debt that hinders maintainability and debuggability. (link)

@sammshen sammshen enabled auto-merge (squash) April 6, 2026 21:01
@github-actions github-actions Bot added the full Run comprehensive tests on this PR label Apr 6, 2026
@sammshen sammshen merged commit 7f32611 into LMCache:dev Apr 6, 2026
47 of 48 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full Run comprehensive tests on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants