| commit | eb32abd8d931994d10327bd965a4fb12d765a0fb | |
| author | Thomas Huth <thuth@redhat.com> | |
| Thu, 6 Aug 2020 10:16:13 +0000 (6 12:16 +0200) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Tue, 6 Oct 2020 18:14:48 +0000 (6 20:14 +0200) | ||
| tree | c656894a3b7adaed12d59cc16eca8d39b5c19509 | treesnapshot (tar.gz zip) |
| parent | 6e05891c31012fccb071cc173ba0f31b09167bba | commitdiff |
tests/qtest/cdrom: Add more s390x-related boot tests
Let's add two new tests:
1) Booting with "bootindex" is the architected default behavior on the
s390x target, so we should have at least one test that is using the
"bootindex" property.
2) The s390-ccw bios used to fail when other unbootable devices have
been specified before the bootable device (without "bootindex"). Now
that the s390-ccw bios is a little bit smarter here, we should test
this scenario, too, to avoid regressions.
Message-Id: <20200806105349.632-10-thuth@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Janosch Frank <frankja@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Let's add two new tests:
1) Booting with "bootindex" is the architected default behavior on the
s390x target, so we should have at least one test that is using the
"bootindex" property.
2) The s390-ccw bios used to fail when other unbootable devices have
been specified before the bootable device (without "bootindex"). Now
that the s390-ccw bios is a little bit smarter here, we should test
this scenario, too, to avoid regressions.
Message-Id: <20200806105349.632-10-thuth@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Janosch Frank <frankja@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| tests/qtest/cdrom-test.c | diffblobblamehistory |