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: stop CPU load monitoring at the end of a test #3620

Merged
merged 2 commits into from
Apr 20, 2023

Conversation

pb8o
Copy link
Contributor

@pb8o pb8o commented Apr 19, 2023

Also remove the CPU load monitoring from Microvm, since this is the only user and it fits better as a Context Manager.

Changes

...

Reason

The assert/error belongs during the test call phase, and not teardown.

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

  • If a specific issue led to this PR, this PR closes the issue.
  • The description of changes is clear and encompassing.
  • Any required documentation changes (code and docs) are included in this PR.
  • API changes follow the Runbook for Firecracker API changes.
  • User-facing changes are mentioned in CHANGELOG.md.
  • All added/changed functionality is tested.
  • New TODOs link to an issue.
  • Commits meet contribution quality standards.

  • This functionality cannot be added in rust-vmm.

We see errors during teardown. It is then not clear if the CPU usage
happened during the call phase of the test (which would be legit) or the
teardown (which would be a false positive).

Restrict the CPU load monitoring part to only the part of the test we
are interested in.

Also remove the CPU load monitoring from Microvm, since this is the only
user and it fits better as a Context Manager.

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
@pb8o pb8o self-assigned this Apr 19, 2023
@pb8o pb8o added Priority: Medium Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled Status: Awaiting review Indicates that a pull request is ready to be reviewed labels Apr 19, 2023
In the SignOff custom commit rule, use the original message to check if
signoff exists, since the line may be ignored otherwise.

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
@pb8o pb8o merged commit 8c26dcf into firecracker-microvm:main Apr 20, 2023
@pb8o pb8o deleted the fix-cpuload branch April 20, 2023 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled Status: Awaiting review Indicates that a pull request is ready to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants