cpu: rv64: rebalance weekly CI test partitions#4955
Merged
Conversation
Co-authored-by: Fei Zhang <zhangfei@iscas.ac.cn>
f3343f8 to
d41a6a2
Compare
Co-authored-by: Fei Zhang <zhangfei@iscas.ac.cn>
zhangfeiv0
approved these changes
Apr 7, 2026
zhangjian29
approved these changes
Apr 8, 2026
vpirogov
approved these changes
Apr 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR rebalances the weekly RISC-V test partitions.
The weekly workflow previously split tests by fixed
ctest -I start,,strideindexing, which led to uneven runtimes and caused some partitions to exceed the 6-hour timeout.This change adds a weighted partitioning mode in the RISC-V test runner and initially uses runtime data from the last successful weekly run to distribute tests more evenly across the 10 weekly jobs, while keeping the existing smoke CI path unchanged.
After the initial rebalance, the runtime weights were refreshed once more using a validation run on my own fork, and the updated results are included here.
Tests missing from the collected runtime data are assigned a default estimated cost of 60 seconds, which keeps the partitioning logic stable for newly added or previously unseen cases.
before
after