Project

General

Profile

Actions

action #120879

closed

Skip execution of `extra_tests_phub` by checking if we're already in GMC phase, skip otherwise.

Added by szarate about 2 years ago. Updated 24 days ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
2022-11-23
Due date:
% Done:

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: November Sprint (Nov 09 - Dec 07)

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

Related issues 5 (0 open5 closed)

Related to openQA Tests - action #120687: [qe-core][functional] test fails in python_flake8 auto_review:"needed by the to be installed python3-flake8":force_result:softfailedResolvedrfan12022-11-17

Actions
Related to openQA Tests - action #115694: [qe-core] test fails in python_flake8: colored output not properly parsed by openQAResolved2022-08-24

Actions
Related to openQA Tests - action #120393: [qe-core][functional] test fails in vmstatResolvedrfan1

Actions
Blocks openQA Tests - action #120486: [qe-core][functional]test fails in add_phub_extensionResolvedrfan1

Actions
Blocks openQA Tests - action #119518: [qe-core] test fails in ansible - Ansible test module needs to be moved to the phub testsuiteResolvedapappas2022-10-28

Actions
Actions #1

Updated by szarate almost 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
Actions #2

Updated by szarate almost 2 years ago

  • Related to action #115694: [qe-core] test fails in python_flake8: colored output not properly parsed by openQA added
Actions #3

Updated by szarate almost 2 years ago

  • Related to action #120486: [qe-core][functional]test fails in add_phub_extension added
Actions #4

Updated by szarate almost 2 years ago

  • Related to deleted (action #120486: [qe-core][functional]test fails in add_phub_extension)
Actions #5

Updated by szarate almost 2 years ago

  • Blocks action #120486: [qe-core][functional]test fails in add_phub_extension added
Actions #6

Updated by szarate almost 2 years ago

  • Blocks action #119518: [qe-core] test fails in ansible - Ansible test module needs to be moved to the phub testsuite added
Actions #7

Updated by rfan1 almost 2 years ago

  • Related to action #120393: [qe-core][functional] test fails in vmstat added
Actions #8

Updated by rfan1 almost 2 years ago

  • Assignee set to rfan1
Actions #9

Updated by rfan1 almost 2 years ago

Based on https://bugzilla.suse.com/show_bug.cgi?id=1202416

The package hub should be ready in Beta phase.

Actions #10

Updated by rfan1 almost 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.

Actions #11

Updated by apappas almost 2 years ago

  • Status changed from Workable to In Progress
Actions #13

Updated by rfan1 almost 2 years ago

  • Status changed from In Progress to Feedback
Actions #14

Updated by rfan1 almost 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

Actions #15

Updated by openqa_review 3 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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #16

Updated by rfan1 3 months ago

  • Status changed from Feedback to Resolved
Actions #17

Updated by openqa_review 3 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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #18

Updated by openqa_review about 2 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:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #19

Updated by rfan1 24 days ago

  • Status changed from Feedback to Resolved

mark it as resolved since it is fixed by other tickets

Actions

Also available in: Atom PDF