Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: unpin m6i/5.10 AMI for perf tests #4983

Merged
merged 3 commits into from
Jan 9, 2025

Conversation

roypat
Copy link
Contributor

@roypat roypat commented Jan 8, 2025

With C-states renabled by f610cae ("fix: stop messing with C-states in performance tests"), the m6i volatility will be gone.

Changes

...

Reason

...

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

With C-states renabled by f610cae ("fix: stop messing with C-states
in performance tests"), the m6i volatility will be gone.

Signed-off-by: Patrick Roy <[email protected]>
pb8o
pb8o previously approved these changes Jan 8, 2025
Copy link

codecov bot commented Jan 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.95%. Comparing base (7e1f3d8) to head (53e0b31).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4983   +/-   ##
=======================================
  Coverage   83.95%   83.95%           
=======================================
  Files         248      248           
  Lines       27839    27839           
=======================================
  Hits        23371    23371           
  Misses       4468     4468           
Flag Coverage Δ
5.10-c5n.metal 84.53% <ø> (ø)
5.10-m5n.metal 84.51% <ø> (+<0.01%) ⬆️
5.10-m6a.metal 83.79% <ø> (ø)
5.10-m6g.metal 80.63% <ø> (ø)
5.10-m6i.metal 84.50% <ø> (ø)
5.10-m7g.metal 80.63% <ø> (ø)
6.1-c5n.metal ?
6.1-m5n.metal 84.51% <ø> (ø)
6.1-m6a.metal 83.79% <ø> (ø)
6.1-m6g.metal 80.63% <ø> (ø)
6.1-m6i.metal 84.51% <ø> (+<0.01%) ⬆️
6.1-m7g.metal 80.63% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Using the larger delay appears to have negative side affects on AMD

Signed-off-by: Jack Thomson <[email protected]>
@roypat roypat marked this pull request as ready for review January 8, 2025 18:05
@roypat roypat requested a review from JackThomson2 January 9, 2025 11:21
@roypat roypat merged commit 0e36ec4 into firecracker-microvm:main Jan 9, 2025
6 of 7 checks passed
@JackThomson2 JackThomson2 mentioned this pull request Jan 9, 2025
10 tasks
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.

5 participants