-
Notifications
You must be signed in to change notification settings - Fork 170
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
domtime: update for s390x #5936
base: master
Are you sure you want to change the base?
Conversation
|
646938a
to
ae796a0
Compare
@@ -3,23 +3,36 @@ | |||
start_vm = no | |||
take_regular_screendumps = "no" | |||
vm_stop_duration = 10 | |||
s390-virtio: | |||
positive: |
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.
I think line 7 ~ line 10 are not necessary since you already add no s390-virtio in respective variant 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.
@chunfuwen You are right there is duplication but the intention of 7-10 is exactly to prevent each variant from having its own 'no s390-virtio', this way all config is in one place. So I removed the subvariant specific 'no s390-virtio' filters.
hwclock is not available on s390x and guest agent operators that modify the time either. 1. Don't try to restore time (with --now flag) during teardown. 2. Disable test cases that try to modify time. 3. Skip step that uses hwclock. Signed-off-by: Sebastian Mitterle <[email protected]>
ae796a0
to
e3b4157
Compare
hwclock is not available on s390x and guest agent operators that modify the time either.