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

toolkit expects %check section to not actually fail package build (when mariner-check-macros is installed) #8181

Open
ddstreetmicrosoft opened this issue Feb 29, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@ddstreetmicrosoft
Copy link
Contributor

The mariner-check-macros rpm (from the mariner-rpm-macros package) installs a macros file macros.check which overrides parts of the rpm build check section operation and intentionally prevents the result of the check section from causing the build to fail.

This is a bad design since normal users would never expect the rpmbuild check section to fail but the build continue and complete successfully. The toolkit code looks back into the log file to try to parse out if the check section failed or not; normal users should not need to do this.

Hence the toolkit design on this point is wrong and needs to be fixed; the rpmbuild check section should not be overridden to cause it to not fail. The toolkit can easily change how it performs rpm builds if it needs to be able to perform build and check operations separately.

@ddstreetmicrosoft ddstreetmicrosoft added the bug Something isn't working label Feb 29, 2024
@ddstreetmicrosoft
Copy link
Contributor Author

@dmcilvaney
Copy link
Contributor

This was a work around for a limitation in the very old build system (mariner1 era). This should be something we can resolve now with the modern build tools since they don't require non-fatal tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants