| commit | 8d4e897a99089995128b78b3c3e61beb4a8e2f23 | |
| author | Daniel P. Berrangé <berrange@redhat.com> | |
| Tue, 28 Jun 2022 10:54:31 +0000 (28 11:54 +0100) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Tue, 5 Jul 2022 07:33:58 +0000 (5 09:33 +0200) | ||
| tree | a553047da08956ed723674ad29f50e6b4406f1f6 | treesnapshot (tar.gz zip) |
| parent | 276dfd03f00358ba904ca1954d3671f94949fbf6 | commitdiff |
tests: wait for migration completion before looking for STOP event
When moving into the convergance phase, the precopy tests will first
look for a STOP event and once found will look for migration completion
status. If the test VM is not converging, the test suite will be waiting
for the STOP event forever. If we wait for the migration completion
status first, then we will trigger the previously added timeout and
prevent the test hanging forever.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
Message-Id: <20220628105434.295905-3-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
When moving into the convergance phase, the precopy tests will first
look for a STOP event and once found will look for migration completion
status. If the test VM is not converging, the test suite will be waiting
for the STOP event forever. If we wait for the migration completion
status first, then we will trigger the previously added timeout and
prevent the test hanging forever.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
Message-Id: <20220628105434.295905-3-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| tests/qtest/migration-test.c | diffblobblamehistory |