Skip to content

Update requested resource for quick CI tests only - #924

Open
jas1005 wants to merge 1 commit into
developfrom
maintenance/ci_resource_allocation_tuning
Open

jas1005 wants to merge 1 commit into
developfrom
maintenance/ci_resource_allocation_tuning

Conversation

@jas1005

@jas1005 jas1005 commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Upper/Lower bounds updated via resource warnings in Jenkins CI dashboard. New reference files introduced as of icarus_ci build 15201, and these bounds were tuned via builds 15211, 15218, and 15222.

Upper/Lower bounds updated via resource warnings in Jenkins CI dashboard. New reference files introduced as of icarus_ci build 15201, and these bounds were tuned via builds 15211, 15218, and 15222.
@jas1005
jas1005 requested review from cerati and vitodb and a lite review from Copilot September 11, 2026 18:37

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Changes recommended

Calibrate or justify the unchanged reco0 thresholds in the active quick-test suite.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates quick CI resource bounds using recent Jenkins calibration data.

Changes:

  • Recalibrates CPU and memory ranges for quick tests.
  • Updates calibration metadata and removes a redundant commented suite entry.
  • Requires updating or documenting the unchanged reco0 thresholds.
File summaries
File Summary
test/ci/ci_tests.cfg Updates quick-test resource limits; reco0 remains on potentially stale thresholds.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread test/ci/ci_tests.cfg
Comment on lines +704 to +706
# Calibrated with [e26] via Jenkins dashboard values on September 10th, 2026
cpu_usage_range=300:500
mem_usage_range=2250000:3500000

@cerati cerati left a comment

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.

I do not see anything wrong, and the change in requirements seem reasonable. Vito might have more insights. Also, I am not sure what the Copilot comment means. But as far as I am concerned this is approved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants