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
rpm: add python3-hirte package #351
Conversation
Building the rpm:
Before installing the module:
Now installing the module via package:
|
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.
If I understood the PyPi parity correctly, we need to publish to pypi first, right? In that case adding this (or at least creating the package on pypi) should be an immediate follow-up, I think, to avoid trouble.
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.
I'm not sure if we should include python module into hirte spec file, wouldn't it be better to have it in a separate spec file? If not, then I think we should try to separate it, so we can skip building python subpackage if needed
@dougsland I think you have one outstanding fix for this so that it can be merged. |
Signed-off-by: Douglas Schilling Landgraf <dougsland@redhat.com>
Which account we create and publish it in PyPi? Also there is a github actions for publishing new releases: |
Error not related to the patch:
|
okay, replied to all questions and points. |
Yes it seems that build -eCONTAINER_USED=integration-test-local has an issue
There is a problem with this container file It seems that this one was merged broken There is an issue with createrepo_c $ARTIFACTS_DIR |
That is the run after the PR has been merged - we run the pipeline on pushes to As far as I can tell, there is no error with the containers (this time). In the pipeline tmt is run with tmt run -eCONTAINER_USED=integration-test-local The build looks fine. It fails when running pytest (before any containers are started) and for some reason the @dougsland As you wrote, this is unrelated to this PR. Please ignore the test failure for now. |
@engelmi some how the repodata does not exist, although logs show it is downloaded. |
On friday # here the resolved rootdir from pytest is one of the test dirs - can't find hirte_test
rootdir: /var/tmp/tmt/run-074/plans/tier0/discover/default-0/tests/tests/tier0/hirte-agent-resolve-fqdn
# when setting confcutdir:
# here the resolved rootdir from pytest is the tests/ as before - works
rootdir: /var/tmp/tmt/run-075/plans/tier0/discover/default-0/tests @ygalblum found the solution for this and created #370 to fix this. @dougsland Could you please reabse? Then it should work now again :) |
Sure, it's possible to skip downstream. |
LGTM |
LGTM |
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.
LGTM
No description provided.