Change ROS spread testing strategy
Metadata
Current evaluation
Abandoned without implementation. The proposal to restrict ROS spread tests to ROS-specific changes or weekly runs was closed, leaving CI optimization unaddressed. No resolution or merge details were provided.
Suggested action: —
No scores available.
Issue body
### What needs to get done
The ROS spread tests are slow and don't need to be run with every PR.
They should only run when:
* ROS-related code changes
* In the weekly spread tests
### Why it needs to get done
To speed up CI runs
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without implementation. The proposal to restrict ROS spread tests to ROS-specific changes or weekly runs was closed, leaving CI optimization unaddressed. No resolution or merge details were provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. A Jira ticket was created to track the proposed CI optimization for ROS spread tests, but no code changes or merge details were provided. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The enhancement to restrict ROS spread tests to ROS changes or weekly runs was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Proposed optimizations to ROS spread testing to reduce CI latency were closed without implementation. The enhancement remains abandoned with no resolution or pull request. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4369 test(spread): make ros linter test less strict | snapcraft | merged | Merged into main after two approvals and passing CI. The change relaxes the ROS linter spread test to properly filter libpng warnings while retaining ros2-humble checks, resolving issue #4256. |