Rebase on upstream most recent version 0.22.0-4 (7c6bb64e550ccfefe4001e79fef44b7d69446c36)#145
Conversation
Previously all exit codes from execution of tests inside container have been ignored and make command ended with zero always. Also drop testing of el7toel8 repository for Python 3.6 on RHEL 8. The test started to fail for unknown reason (changes in pytest or another nonstandard python module?). As we are in the middle of dropping all el7toel8 and python2 related content, let's just drop it. Keeping the full removal of Py2 and el7toel8 content on separate PR. (cherry picked from commit 397975d)
Previous name have been very long, repeating, and it has been problem to read the whole informatino about what tests are performed as the description has been shortened in WebUI, e.g.: Unit Tests / Run unit tests in containers (Run python linters for el8toel9 and common repositories on p... Let's change the name so it's shortened and easier read what test has been actually performed. Also, no need to mention that tests are running in container anymore, as we are not running unit-tests outside of the container in upstream. Example of new style names: Unit Tests / Run: Linters (python:3.9; repos:el9toel10,common) (pull_request) Unit Tests / Run: Unit Tests (python:3.9; repos:el9toel10,common) (pull_request) (cherry picked from commit 4e87908)
Original parsing has been splitting string tokens by "=" without a limit, means that e.g. root=UUID=some-id has been split to (root, UUID, some-id) and and stored just "root" and "UUID" strings in the parsed msg, instead of "root" and "UUID=some-id". So split the key=value just based on the first occurence of "=" instead. JIRA: RHELMISC-12490 Co-Authored-By: Karolina Kula <kkula@redhat.com> (cherry picked from commit 2646484)
The original solution expect just IPU of RHEL systems and so only source RHEL DNF repositories have been mapped to the target RHEL repositories. Making this more distro agnostic for CentOS-like systems, the mapping needs to be updated to respect distro specific repositories. Hence a 'distro' field has been added in the 1.3.0 version of the repomap.json format. The field is required for all the `repositories` entries. RepomapDataHandler now takes in distro as a constructor parameter and only consider entries with the matching distro value. Reflects also changes in the repomap json schema for version 1.3.0, which drops enumeration for the `rhui` field and replace it by simple String type to make the solution more scalable. This also means that vendor of the repomap data file must validate this field "manually". All related unit-tests have been updated. As the commit is already large, keeping the update of data files on a separate commit. Update the PESIDRepositoryEntry model: * add the distro field represented by String * change rhui type from StringEnum to String Jira: RHEL-80336 WIP setuptarget repos tests for distro Add repositories mapping unit tests for distro (cherry picked from commit ff21cc8)
The repomap file has the new format version 1.3.0 which is incompatible with previous versions. At this point, let's draw a line here to switch to require data stream 4.0+ to omit possible issues with previous data files. Signed-off-by: Petr Stodulka <pstodulk@redhat.com> (cherry picked from commit 2544f57)
The deprecation warning is not wanted in unit-tests. Supress it. Signed-off-by: Petr Stodulka <pstodulk@redhat.com> (cherry picked from commit 6c20528)
* tmt-tests.yml and reuse-copr-build.yml were replaced by the Packit workflows ages ago * removed the obsolete workflows Signed-off-by: Daniel Diblik <ddiblik@redhat.com> (cherry picked from commit c7ea9fc)
The Leapp team is not available on IRC anymore. We advise the public to talk to us on GitHub instead. (cherry picked from commit 7c6bb64)
Thank you for contributing to the Leapp project!Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build.
Note that first time contributors cannot run tests automatically - they need to be started by a reviewer. It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported,
See other labels for particular jobs defined in the Please open ticket in case you experience technical problem with the CI. (RH internal only) Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra. |
No description provided.