Closed Venefilyn closed 1 month ago
Attention: Patch coverage is 79.72973%
with 30 lines
in your changes missing coverage. Please review.
Project coverage is 96.09%. Comparing base (
d603f04
) to head (943cec0
). Report is 2 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit build
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test --labels sanity
/packit test
/packit test
/packit test
The changes look great! I see the integration tests are failing and some of them related to the expected messages, maybe something got messed up? I can't see it. For example in integration tests in CentOS7 it expects to see CUSTOM_REPOSITORIES_ARE_VALID::UNABLE_TO_ACCESS_REPOSITORIES but instead C2R fails with:
convert2rhel("-y --no-rhsm --enablerepo fake-rhel-8-for-x86_64-baseos-rpms --debug", unregister=True)
(ERROR) REMOVE_SPECIAL_PACKAGES::SPECIAL_PACKAGE_REMOVAL_FAILED - Failed to remove some packages necessary for the conversion. Description: The cause of this error is unknown, please look at the diagnosis for more information. Diagnosis: Couldn't download the centos- release-7-9.2009.2.el7.centos.x86_64 package. This means we will not be able to do a complete rollback and may put the system in a broken state. Check to make sure that the CentOS Linux repositories are enabled and the package is updated to its latest version.
@SerCantus is it occurring in other PRs or in main?
/packit test
@SerCantus is it occurring in other PRs or in main?
@Venefilyn I commented after reviewing this PR checks but I see other PRs have similar failures so it might not be caused by this one. After discussing, it might be related to some infra.
Ack, feel free to approve and merge with squash
This refactor of the usage of our logging is to get away from custom functions that causes attribute errors in editors and IDEs. This will also standarize the usage of logger and the loglevels.
In future PRs we can include changes to include prepare, rollback, and final specific message styles.
Jira Issues:
-
Depends on
1327
Checklist
[RHELC-]
or[HMS-]
is part of the PR titleRelease Pending
if relevant