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
Move yast2 lan tests to YaST job group #10228
Merged
Merged
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
jknphy
changed the title
[WIP] Move yast2 lan yast group
[WIP] Move yast2 lan tests to YaST job group
May 11, 2020
jknphy
force-pushed
the
move_yast2_lan_yast_group
branch
6 times, most recently
from
May 11, 2020 14:00
da48817
to
6d4c1f1
Compare
rwx788
reviewed
May 11, 2020
jknphy
force-pushed
the
move_yast2_lan_yast_group
branch
4 times, most recently
from
May 12, 2020 07:42
7f89b56
to
117a61c
Compare
jknphy
changed the title
[WIP] Move yast2 lan tests to YaST job group
Move yast2 lan tests to YaST job group
May 14, 2020
jknphy
force-pushed
the
move_yast2_lan_yast_group
branch
2 times, most recently
from
May 14, 2020 10:31
76a4d2e
to
3fec274
Compare
jknphy
force-pushed
the
move_yast2_lan_yast_group
branch
from
May 14, 2020 12:31
3fec274
to
33c9504
Compare
b10n1k
reviewed
May 18, 2020
b10n1k
requested changes
May 18, 2020
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.
only one things and i thing is good to go
jknphy
force-pushed
the
move_yast2_lan_yast_group
branch
from
May 18, 2020 06:34
33c9504
to
2b36eef
Compare
rwx788
reviewed
May 18, 2020
jknphy
force-pushed
the
move_yast2_lan_yast_group
branch
2 times, most recently
from
May 19, 2020 05:33
50a6a73
to
f55a26a
Compare
Move yast2 lan tests to YaST job group trying to match the closer test coverage to the existing one and therefore excluding this test module from the default schedule of main.pm mechanism for latest product to have more control on its maintenance. Currently when the module is schedule in other arch than x86_64 we are just opening it, so with this change we can apply the detailed check for all architectures.
jknphy
force-pushed
the
move_yast2_lan_yast_group
branch
from
May 19, 2020 05:34
f55a26a
to
87e5f53
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.
Move yast2 lan tests to YaST job group trying to match the closer test coverage to the existing one and therefore excluding this test module from the default schedule of main.pm mechanism for latest product to have more control on its maintenance.
Currently in functional group when the module is schedule in other architecture than x86_64 we are just opening it, so with this change we can apply the detailed check for aarch64 and ppc64le. For s390x after creating a few needles there are still failures so there it is enabled just the current light check.