TMT: Simplify plans #1684
Merged
TMT: Simplify plans #1684
Conversation
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
|
Rawhide tests are failing on unrelated issues, likely a faulty new distro compose. We can ignore it for now. |
The same set of tests are being run upstream and downstream. Enablement of podman-next copr for bleeding-edge testing is handled by plans/main.fmf and .packit.yaml automatically so there's no additional need to specify `/upstream` and `/downstream`. Also, no need to for a redundant `/system-test` inside test/tmt/podman/system-test.fmf. Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
force-pushed
the
tmt-simplify-plans
branch
from
b54bb10 to
7b910ea
Compare
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.
The same set of tests are being run upstream and downstream.
Enablement of podman-next copr for bleeding-edge testing is handled by plans/main.fmf and .packit.yaml automatically so there's no additional need to specify
/upstreamand/downstream.