Skip to content

[CI] Add artifact upload for 4-card test error logs#7034

Open
EmmonsCurse wants to merge 2 commits intoPaddlePaddle:developfrom
EmmonsCurse:add_error_logs_upload
Open

[CI] Add artifact upload for 4-card test error logs#7034
EmmonsCurse wants to merge 2 commits intoPaddlePaddle:developfrom
EmmonsCurse:add_error_logs_upload

Conversation

@EmmonsCurse
Copy link
Copy Markdown
Collaborator

Motivation

CI logs are often insufficient for debugging 4-card distributed test failures, especially due to truncated outputs and fragmented logs. This makes some issues hard to diagnose or reproduce locally.

Modifications

  • Add artifact upload for full error logs when TEST_EXIT_CODE == 8
  • Upload run_4_cards_tests_error_logs for debugging
  • Set retention to 7 days and ignore missing files

Usage or Command

N/A

Accuracy Tests

N/A

Checklist

  • Add at least a tag in the PR title.
    • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
    • You can add new tags based on the PR content, but the semantics must be clear.
  • Format your code, run pre-commit before commit.
  • Add unit tests. Please write the reason in this PR if no unit tests.
  • Provide accuracy results.
  • If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

@EmmonsCurse
Copy link
Copy Markdown
Collaborator Author

/skip-ci ci_iluvatar
/skip-ci ci_hpu
/skip-ci build_xpu
/skip-ci coverage
/skip-ci pre_ce_test
/skip-ci stable_test
/skip-ci base_test
/skip-ci logprob_test

@paddle-bot
Copy link
Copy Markdown

paddle-bot bot commented Mar 26, 2026

Thanks for your contribution!

@paddle-bot paddle-bot bot added the contributor External developers label Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor External developers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant