-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Bug] ./tools/devtool test
fails on non-ec2 machines
#3726
Comments
The test_rng should be fixed soon with some changes I have. The other ones related to performance baselines could be fixed by moving the baseline loading file into the |
Yeah, for the baseline things, I plan to add that change to #3736 :) |
For the block test, the baselines thing hasnt been fixed yet |
this caused pytest to crash during test collection if running on an unsupported kernel version. Fixes firecracker-microvm#3726 Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
this caused pytest to crash during test collection if running on an unsupported kernel version. Fixes firecracker-microvm#3726 Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
this caused pytest to crash during test collection if running on an unsupported kernel version. Fixes firecracker-microvm#3726 Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Describe the bug
Attempting to run our integration tests on a non-ec2 machine (e.g. local dev laptop) yields
The first one is due to
test_rng.py
unconditionally trying to make IMDS request to determine instance type and then checking which tests to skip. The other two are due to my ubuntu laptop having kernel 5.19 instead of 4.14 or 5.10. However, since performance tests are marked as "nonci", they wouldn't've run anyway, so this error should probably just be ignored.To Reproduce
Run
./tools/devtool test
outside of EC2, or with a kernel version thats not 4.14 or 5.10Expected behaviour
Tests to run
Environment
Checks
The text was updated successfully, but these errors were encountered: