e2e: Continue verify after a failed portage check#89
Merged
Conversation
The "elogviewer is available in portage" check runs emerge --pretend against the official ebuild and can fail whenever Gentoo's stage3 default Python moves ahead of the ebuild's PYTHON_COMPAT — expected drift, not a bug, since e2e is meant to track live Gentoo defaults. It previously aborted verify.yml immediately, skipping the more direct check further down that builds the current sdist and runs the actual pytest suite under whatever Python is installed. The check is now ignored and re-asserted as a final task, so the rest of the play still runs before failing.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.