Project

General

Profile

Actions

action #133529

open

libqca2: legacy providers give an error

Added by dimstar 9 months ago. Updated 4 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-07-29
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:

Description

Observation

This happens after the latest upgrade of qca to version 2.3.7:
https://build.opensuse.org/request/show/1101014/changes

openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in
libqca2

Test suite description

Same as jeos, plus some more tests.

Reproducible

Fails since (at least) Build 20210824

Expected result

Last good: 20210823 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by maritawerner 9 months ago

  • Tags set to qac
Actions #2

Updated by openqa_review 9 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: extra_tests_textmode
https://openqa.opensuse.org/tests/3504545#step/java/1

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 #3

Updated by openqa_review 7 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: extra_tests_textmode
https://openqa.opensuse.org/tests/3590895#step/command_not_found/1

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 #4

Updated by openqa_review 5 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: extra_tests_textmode
https://openqa.opensuse.org/tests/3787841#step/java/1

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 152 days if nothing changes in this ticket.

Actions #5

Updated by dimstar 4 months ago

  • Status changed from New to Rejected

Moved to a product bug after debugging it: https://bugzilla.opensuse.org/show_bug.cgi?id=1218254

Actions #6

Updated by openqa_review 4 months ago

  • Status changed from Rejected 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: extra_tests_textmode
https://openqa.opensuse.org/tests/3868106#step/aaa_base/1

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 48 days if nothing changes in this ticket.

Actions

Also available in: Atom PDF