Dump debug info when accessing the rpm_spec property
#397
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Nikola Forró <[email protected]>
|
Build succeeded. ✔️ pre-commit SUCCESS in 2m 09s |
|
/packit test |
|
/packit-stg test |
|
/packit test |
|
/packit-stg test |
|
/packit test |
|
/packit-stg test |
|
Desperately trying to trigger the exception in TF 😅 |
|
/packit test |
|
/packit-stg test |
|
/packit test |
|
/packit-stg test |
|
/packit test |
|
/packit-stg test |
|
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 2m 07s |
softwarefactory-project-zuul bot
added a commit
to packit/packit
that referenced
this pull request
Aug 29, 2024
Capture specfile debug logs in selected tests Related to packit/packit-service#2461, packit/specfile#397. Reviewed-by: Maja Massarini
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to packit/packit-service#2461.
I'm not sure if this will help, but it's better than nothing. I'm still unable to reproduce the exception locally.