-
Notifications
You must be signed in to change notification settings - Fork 83
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
Arange tests in tiers #343
Conversation
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.
I have a couple of questions\remarks:
- How do I run single tests in your approach? Like I want to run just a NetworkManager test, how do I do it?
- With tests from tierN running on 1 guest this causes the need for us to track what is actually happening in an SST test, if there are any changes from the last version and if they are destructive (meaning the test can't be run in a tierN anymore). Is the speedup really worth the management complexity it brings? I really loved the "I don't care what's inside" approach to be honest :(
- How do we mark destructive tests (the one that should be run 1 test per vm)? By not adding them to tiers?
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.
Just few things:
- those "env_from" files are there for some reason?
- I don't like the specification of those tiers, I would swap tier1 and tier0 as those these tests in tier1 are more "basic" and should be run more often. Also some tests in tier0 already do the full conversion (eg. "changed_yum_conf"). However that's just my opinion.
Otherwise I like splitting tests into tiers))
discover+: | ||
test: changed-yum-conf | ||
|
||
/check_custom_repo: |
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.
We need to add the preparation role that adds custom repos on the target machine
discover+: | ||
test: inhibit-if-kmods-is-not-supported | ||
|
||
/inhibit_if_oracle_system_uses_not_standard_kernel: |
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.
Now this plans is only for Centos8, we should not run this one as it's oracle specific
- name: reboot machine | ||
how: ansible | ||
playbook: tests/ansible_collections/reboot.yml | ||
|
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.
Bear in mind that these tests:
- "resolve-dependency" from "rhsm" conversion folder
- "one-kernel-scenarion" from "custom-repos" conversion folder
They need some extra preparation steps. Maybe we could move them to the tier0?
6ee3889
to
b9fff61
Compare
Based on your Packit configuration the settings of the @oamg/convert2rhel Copr project would need to be updated as follows:
Packit was unable to update the settings above as it is missing To fix this you can do one of the following:
Please retrigger the build, once the issue above is fixed. |
Based on your Packit configuration the settings of the @oamg/convert2rhel Copr project would need to be updated as follows:
Packit was unable to update the settings above as it is missing To fix this you can do one of the following:
Please retrigger the build, once the issue above is fixed. |
1380fa6
to
13ca0ae
Compare
The tests are failing on pytest conftest.py:
It seems the |
c3699ce
to
f0d542e
Compare
0276dd6
to
9908d7a
Compare
8ee45dd
to
63265ed
Compare
6e9d761
to
e4fa3b3
Compare
So the situation is that currently we are able to run only tier0 and tier1 tests on testing farm for Centos7 and Centos8. OracleLinux images have some issues so we decided to disable them until we fix them. |
Yes, you are right. I was overthinking about that condition xD |
Rearanging the test plans to follow tiers structure like this: - tier0 = tests running on source system (the system is not converted) - tier1 = tests running on target system (the system is converted) - tier2 = tests of other components in convert workflow - Disable broken rollback test fot centos-7
Broken rollback test is disabled for centos-7 until the OAMG-5455 is done. |
oh, I can not merge it :-( I am technically still an author. @bocekm could you please approve and merge it? |
Rearanging the test plans to follow tiers structure like this: