-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add pkg_tester #4818
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
Add pkg_tester #4818
Conversation
sfc-gh-mpilman
left a comment
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.
There is already something similar in build/cmake/package_tester -- can you please either:
- Use that one or
- Add a note why not and delete the old one?
Having to test systems for this seems to be overkill.
da529c8 to
1ea5875
Compare
1ea5875 to
82d0ef7
Compare
The |
sfc-gh-abeamon
left a comment
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.
This looks reasonable to me, and if I understand correctly from the commit history it seems to have already helped you identify some problems with the packages. I notice there's one comment from Markus about the gitignore file, do you intend to use his suggestion?
sfc-gh-anoyes
left a comment
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.
This looks reasonable to me, and if I understand correctly from the commit history it seems to have already helped you identify some problems with the packages. I notice there's one comment from Markus about the gitignore file, do you intend to use his suggestion?
Suggestion taken. PTAL
This review is no longer relevant since the build/ dir was deleted
Cherry pick (#4818) - pkg_tester and packaging fixes (release-6.3)
Recently we've been having some problems with our packaging (e.g. #4731 ). This PR adds some basic tests we can run to check that our generated rpm and deb packages behave as expected after making packaging changes.
I tested leaking docker images/containers by running the tests and interrupting them with ctrl-c. These tests do a pretty good job, but I added some instructions to the README about what to do just in case.
This change now also incorporates the fixes from #5391, and adds tests for the versioned packages.
Code-Reviewer Section
The general guidelines can be found here.
Please check each of the following things and check all boxes before accepting a PR.
For Release-Branches
If this PR is made against a release-branch, please also check the following:
release-branchormasterif this is the youngest branch)