Skip to content
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

Merged
merged 1 commit into from
Nov 3, 2021
Merged

Arange tests in tiers #343

merged 1 commit into from
Nov 3, 2021

Conversation

mkluson
Copy link
Member

@mkluson mkluson commented Sep 10, 2021

Rearanging the test plans to follow tiers structure like this:

  • tier0 = tests running on source system
  • tier1 = test running on target system
  • tier2 = test of other components in convert workflow

@Venefilyn Venefilyn marked this pull request as draft September 10, 2021 14:57
Copy link
Member

@fernflower fernflower left a 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:

  1. How do I run single tests in your approach? Like I want to run just a NetworkManager test, how do I do it?
  2. 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 :(
  3. How do we mark destructive tests (the one that should be run 1 test per vm)? By not adding them to tiers?

plans/tier0.fmf Outdated Show resolved Hide resolved
@bocekm bocekm mentioned this pull request Sep 13, 2021
2 tasks
Copy link
Member

@kokesak kokesak left a 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:
Copy link
Member

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:
Copy link
Member

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

Copy link
Member

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?

@kokesak kokesak force-pushed the to_show branch 3 times, most recently from 6ee3889 to b9fff61 Compare September 17, 2021 09:00
@packit-as-a-service
Copy link

Based on your Packit configuration the settings of the @oamg/convert2rhel Copr project would need to be updated as follows:

field old value new value
chroots ['epel-6-x86_64', 'epel-7-x86_64', 'epel-8-x86_64', 'oraclelinux-7-x86_64', 'oraclelinux-8-x86_64'] ['epel-6-x86_64', 'epel-8-x86_64', 'epel-7-x86_64']

Packit was unable to update the settings above as it is missing admin permissions on the @oamg/convert2rhel Copr project.

To fix this you can do one of the following:

  • Grant Packit admin permissions on the @oamg/convert2rhel Copr project on the permissions page.
  • Change the above Copr project settings manually on the settings page to match the Packit configuration.
  • Update the Packit configuration to match the Copr project settings.

Please retrigger the build, once the issue above is fixed.

@packit-as-a-service
Copy link

Based on your Packit configuration the settings of the @oamg/convert2rhel Copr project would need to be updated as follows:

field old value new value
chroots ['epel-6-x86_64', 'epel-7-x86_64', 'epel-8-x86_64', 'oraclelinux-7-x86_64', 'oraclelinux-8-x86_64'] ['epel-6-x86_64', 'epel-8-x86_64', 'epel-7-x86_64']

Packit was unable to update the settings above as it is missing admin permissions on the @oamg/convert2rhel Copr project.

To fix this you can do one of the following:

  • Grant Packit admin permissions on the @oamg/convert2rhel Copr project on the permissions page.
  • Change the above Copr project settings manually on the settings page to match the Packit configuration.
  • Update the Packit configuration to match the Copr project settings.

Please retrigger the build, once the issue above is fixed.

@kokesak kokesak force-pushed the to_show branch 4 times, most recently from 1380fa6 to 13ca0ae Compare September 17, 2021 11:56
@bocekm
Copy link
Member

bocekm commented Sep 17, 2021

The tests are failing on pytest conftest.py:

Warning: Permanently added '10.29.163.132' (ECDSA) to the list of known hosts.

ImportError while loading conftest '/var/ARTIFACTS/work-changed_yum_confqgGEXm/plans/tier0/changed_yum_conf/discover/default/tests/tests/integration/conftest.py'.
../conftest.py:26: in <module>
    logging.basicConfig(level="DEBUG" if env.str("DEBUG") else "INFO", stream=sys.stderr)
/usr/local/lib/python3.6/site-packages/envparse.py:35: in method
    return self.__call__(var, cast=cast, **kwargs)
/usr/local/lib/python3.6/site-packages/envparse.py:99: in __call__
    raise ConfigurationError(error_msg)
E   envparse.ConfigurationError: Environment variable 'DEBUG' not set.

It seems the env.str("DEBUG") raises an Exception when the requested env var is not set, which is not what we need.
We apparently use this library https://github.com/rconradharris/envparse which is not documented (at least I can't find any documentation). I'd say we should use something more standard.

@kokesak kokesak force-pushed the to_show branch 7 times, most recently from c3699ce to f0d542e Compare September 23, 2021 12:54
@kokesak kokesak force-pushed the to_show branch 2 times, most recently from 0276dd6 to 9908d7a Compare October 4, 2021 09:49
@kokesak kokesak force-pushed the to_show branch 6 times, most recently from 8ee45dd to 63265ed Compare October 19, 2021 10:20
@kokesak kokesak force-pushed the to_show branch 3 times, most recently from 6e9d761 to e4fa3b3 Compare October 25, 2021 12:59
@kokesak kokesak marked this pull request as ready for review October 25, 2021 13:02
@kokesak
Copy link
Member

kokesak commented Oct 25, 2021

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.
Tier2 tests are disabled as it is not mandatory to have them working now.

@kokesak
Copy link
Member

kokesak commented Oct 26, 2021

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
@kokesak
Copy link
Member

kokesak commented Nov 1, 2021

Broken rollback test is disabled for centos-7 until the OAMG-5455 is done.

@kokesak kokesak changed the title WIP: Arange tests in tiers Arange tests in tiers Nov 1, 2021
@mkluson
Copy link
Member Author

mkluson commented Nov 1, 2021

oh, I can not merge it :-( I am technically still an author. @bocekm could you please approve and merge it?

@r0x0d r0x0d mentioned this pull request Nov 1, 2021
@bocekm bocekm merged commit 9722e12 into oamg:main Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants