-
Notifications
You must be signed in to change notification settings - Fork 115
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
PIT markers for Interoperability Testing: CapsuleContent #15892
Conversation
trigger: test-robottelo |
PRT Result
|
^^ BrokerError for 3/3 API cases, rebuilding |
PRT Result
|
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.
Right now we don't mark pit_server
for the test which uses *_capsule_configured
fixture, right @ogajduse ?
That is correct. Good catch. @damoore044 please see: #15756 (review) |
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.
ack pending prt
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.
@pytest.mark.pit_server
is not applicable as per previous offline communication, please remove.
d64f32f
to
a2b4c07
Compare
trigger: test-robottelo |
PRT Result
|
The one failing test in above PRT is expected for now due to BZ, |
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
a2b4c07
to
650bd55
Compare
…#15892) PIT markers for interop, CapsuleContent
…#15892) PIT markers for interop, CapsuleContent
Proposing PIT markers added to these CapsuleContent tests