Skip to content

Conversation

@nforro
Copy link
Member

@nforro nforro commented Feb 18, 2025

Even after actions that return some output because even those can modify spec files.
Reload the dist-git spec file also after manipulating the repo for PR creation/update.

Related to #2521.

@softwarefactory-project-zuul

This comment was marked as outdated.

@softwarefactory-project-zuul

This comment was marked as outdated.

Even after actions that return some output because even those
can modify spec files.
Reload the dist-git spec file also after manipulating the repo for
PR creation/update.

Signed-off-by: Nikola Forró <[email protected]>
@softwarefactory-project-zuul
Copy link
Contributor

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/74e4824881834b9ab2cc3b15d21867eb

✔️ pre-commit SUCCESS in 2m 07s
packit-tests-rpm FAILURE in 21m 15s
packit-tests-pip-deps FAILURE in 21m 24s
packit-tests-git-main FAILURE in 21m 45s
✔️ packit-tests-pip-deps-sess-rec SUCCESS in 2m 43s
✔️ packit-tests-git-main-sess-rec SUCCESS in 2m 52s
✔️ reverse-dep-packit-service-tests SUCCESS in 4m 29s

softwarefactory-project-zuul bot added a commit that referenced this pull request Apr 4, 2025
… fixture (#2580)

Initiate dist-git repo after spec file is present in `cockpit_ostree` fixture

The spec file is copied to the dist-git repo after it is initialized, which means it isn't commited to git and eventually gets removed, but that doesn't make the tests fail because the related Specfile instance keeps its content in memory even though the file no longer exists. That however changes once the Specfile instance gets properly reloaded when needed and the tests start to fail. Fix that.
Related to #2532, packit/specfile#458.

Reviewed-by: Laura Barcziová
Reviewed-by: Matej Focko
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.

1 participant