action #120879
closedSkip execution of `extra_tests_phub` by checking if we're already in GMC phase, skip otherwise.
0%
Description
We know that most of the time PackageHub, is only ready super late in the development
Acceptance Criteria¶
add_phub_extension
checks early if we're in GMC phase, if we aren't, kill the test and force a soft failure linking to this ticket
Updated by szarate about 2 years ago
- Related to action #120687: [qe-core][functional] test fails in python_flake8 auto_review:"needed by the to be installed python3-flake8":force_result:softfailed added
Updated by szarate about 2 years ago
- Related to action #115694: [qe-core] test fails in python_flake8: colored output not properly parsed by openQA added
Updated by szarate about 2 years ago
- Related to action #120486: [qe-core][functional]test fails in add_phub_extension added
Updated by szarate about 2 years ago
- Related to deleted (action #120486: [qe-core][functional]test fails in add_phub_extension)
Updated by szarate about 2 years ago
- Blocks action #120486: [qe-core][functional]test fails in add_phub_extension added
Updated by szarate about 2 years ago
- Blocks action #119518: [qe-core] test fails in ansible - Ansible test module needs to be moved to the phub testsuite added
Updated by rfan1 about 2 years ago
- Related to action #120393: [qe-core][functional] test fails in vmstat added
Updated by rfan1 about 2 years ago
Based on https://bugzilla.suse.com/show_bug.cgi?id=1202416
The package hub should be ready in Beta phase.
Updated by rfan1 about 2 years ago
Given the fact that, there some tests which need packagehub in activated status.
I will try to add a variable to skip the chain tests if packagehub is not ready.
Updated by apappas about 2 years ago
- Status changed from Workable to In Progress
Updated by rfan1 about 2 years ago
Updated by rfan1 about 2 years ago
- Status changed from Feedback to Resolved
https://openqa.suse.de/tests/10088351
The test is passed with a known failure for python3_flake8 test
Updated by openqa_review 4 months ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: stack_tests_python
https://openqa.suse.de/tests/15233702
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by openqa_review 4 months ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: stack_tests_python
https://openqa.suse.de/tests/15292090
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by openqa_review 3 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: stack_tests_python
https://openqa.suse.de/tests/15532955
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Updated by rfan1 about 2 months ago
- Status changed from Feedback to Resolved
mark it as resolved since it is fixed by other tickets