-
Notifications
You must be signed in to change notification settings - Fork 114
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
[6.15.z] Eval CapsuleContent::API Assertion Errors, time delta/format in 'wait_for_sync()' #14412
[6.15.z] Eval CapsuleContent::API Assertion Errors, time delta/format in 'wait_for_sync()' #14412
Conversation
trigger: test-robottelo |
PRT Result
|
PRT Result
David- Single Failure is |
trigger: test-robottelo |
b49d469
to
17bf812
Compare
trigger: test-robottelo |
|
17bf812
to
a2d9138
Compare
trigger: test-robottelo |
a2d9138
to
5c1dc7f
Compare
Build [6135] is listed as a failure, but this is because there was an error finding the test report file generated. From console output we can see that 22/22 API tests (all for this module) passed as expected in 6135:
|
PRT Result
|
Cherrypick of PR: #14066
Problem Statement
4 Failures in recent runs of API::CapsuleContent, for
AssertionError
:Locally I can see the
last_sync_time
format from logs as:Solution
last_sync_time
(check if None /Falsey first), then checking length of any in-progress sync tasks, avoiding possibly ambiguous assertion- wherelast_sync_time
has not updated with a recent task, and is still an old sync time/None.The prior
Assertions
with AND, OR, etc fail without showing the compared values. Provided error messages with assertion failure details.start_time
, due to rounding. Often the assertion fails for one second delta, which is start time recorded and sync done at pretty much the same time, but the seconds fromsync_status
were rounded to one second beforestart_time
. This is inconsistent, depending on the milliseconds whenlast_sync_time
is recorded.dateutil.parser
, useparse(date-time string)
method on thestart_time
, and any foundlast_sync_time
. So when checking the last sync time is newer, parse will account for different formats of the same time. Similar solution to PR Fix Date assertion failure in CI errata:e2e #13121Related Issue >> From 'sat-6.15-rhel8-Capsule-Content'
4 Failed api scenarios due to the
AssertionError
in this method. Inconsistently, others will fail locally for the same error.6.14.z and 6.15.0 (most recent Build 13, Mar 7 2024, 12:43 AM)
PRT Case