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

test: fix installation of right package in smoke tests #231

Merged
merged 2 commits into from
Jan 27, 2023

Conversation

pvoborni
Copy link
Contributor

The smoke test is uninstalling all packages and then trying to install them again to check if dependencies work correctly.

The issue is that version of package created by packit on pull request could be lower from dnf PoV than the one available e.g. in EPEL thus the EPEL version is used istead of the one which we are testing.

Thus c8s test is failing as it is picking up a package which has incorrect dependencies.

This PR is recording the initially installed package version to use it again on reinstallation and thus avoid the issue.

Signed-off-by: Petr Vobornik [email protected]

@pvoborni pvoborni force-pushed the fix-rhel8-tests branch 2 times, most recently from 11a2a87 to 0109d1f Compare January 26, 2023 19:44
As it is failing and it needs more time to fix.

Signed-off-by: Petr Vobornik <[email protected]>
Copy link
Member

@Tiboris Tiboris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix and workaround. I have created issue from the pylint.

Thus making the Release higher than the one in repos and thus tmt
in tf/packit integration will prefer the packages from packit.

Signed-off-by: Petr Vobornik <[email protected]>
@pvoborni
Copy link
Contributor Author

I've updated it yet-again as dev.{PACKIT_PROJECT_BRANCH} was still lower than e.g. someting which started with 1.

$ rpmdev-vercmp 1.12.3-dev.pr231 1.12.3-1.20230126174817469017.pr231.4.g887f46d
1.12.3-dev.pr231 < 1.12.3-1.20230126174817469017.pr231.4.g887f46d

$ rpmdev-vercmp 1.12.3-99.dev.pr231 1.12.3-1.20230126174817469017.pr231.4.g887f46d
1.12.3-99.dev.pr231 > 1.12.3-1.20230126174817469017.pr231.4.g887f46d

@pvoborni
Copy link
Contributor Author

In general, I think that we have 2 ways to solve the issue

  • either have high release number, e.g. the 99 as proposed here. The Q is whether it should be in spec or packit config. I chose packit config as I was not sure how koji update works with it and thus 'pull_request' in packit config should not affect it
  • alternative solution would be to have higher version in git than the last release. I.e. bump it after release, but this may not work well with semantic releases functionality (assuming here). Thus the former was chosen.

@pvoborni pvoborni merged commit 72b9b9c into neoave:main Jan 27, 2023
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.

2 participants