-
Notifications
You must be signed in to change notification settings - Fork 437
T8065: Dehardcode qemu settings to allow run tests on arch arm64 #1073
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
base: current
Are you sure you want to change the base?
Conversation
|
👍 |
faa1b8a to
be1db15
Compare
|
@asklymenko add your review, please |
|
@huihuimoe, do you have a chance to check it? |
16b0ef3 to
582f2e3
Compare
1e3e98c to
4fb2337
Compare
| .ONESHELL: | ||
| test-no-interfaces-no-vpp: checkiso | ||
| scripts/check-qemu-install --debug --configd --smoketest --uefi --no-interfaces --no-vpp build/live-image-amd64.hybrid.iso | ||
| scripts/check-qemu-install --debug --configd --smoketest --uefi --no-interfaces --no-vpp --arch $(arch) build/live-image-$(arch).hybrid.iso |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why pass arch explicitly? It could be derived from the image name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because depends on arch we set specific to architecture qemu commands in the “check-qemu-install” script. Image name will not help here
Change summary
Dehardcode qemu settings to allow running smoketests on the arch
arm64I cannot completely check it, due to a lack of arm64 devices with a supported
/dev/kvmBut it is a good starting point. It could still fail on the arm64, but at least we allow it for future investigation.
Types of changes
Related Task(s)
Related PR(s)
#1074
Checklist: