-
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
6.15.z update scope of fixtures from hosts-content longrun test_inc_updates #14843
6.15.z update scope of fixtures from hosts-content longrun test_inc_updates #14843
Conversation
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
bd48486
to
b38d41b
Compare
trigger: test-robottelo |
PRT Result
|
b38d41b
to
dcb6289
Compare
trigger: test-robottelo |
PRT Result
|
|
PRT Result
|
trigger: test-robottelo |
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.
@vijaysawant It seems the other test for this module you're trying to run also,
test_positive_noapply_api
fails in the host
fixture (@L134).
Trying to install katello-host-tools on a rhel7_contenthost_module
fixture (outdated),
to get that one fixed we might want to change host
fixture to use rhel_contenthost
parameterized for rhel version, like with errata hosts?
But since you only changed org fixture for test_positive_noapply_api
in these changes, probably non-blocking. Thoughts?
It's not woking with
|
@vijaysawant Gotcha, we should also try to remove line in |
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 passing robottelo runner
Problem Statement
longrun/test_inc_updates.py
has 2 tests, module scope fixture creates one organization and same organization has been used in two test cases, after uploading manifest second time test was failing due to below error messagetest name: test_positive_incremental_update_time
Error:
['Owner has already imported from another subscription management application. The following conflicts were found: [ DISTRIBUTOR_CONFLICT ]']
Solution
changed scope of fixture of one test case so it will not use previously created organization from same test session.
Related Issues
6.14.z PR #14842
PRT test Cases example
trigger: test-robottelo
pytest: tests/foreman/longrun/test_inc_updates.py