action #117331
closed[qe-core] test fails in python_pycairo
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-extra_tests_textmode@aarch64 fails in
python_pycairo
Test suite description¶
Maintainer: slindomansilla@suse.de.
Mainly post-installation console extra tests.
Reproducible¶
Fails since (at least) Build 20210901
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by maritawerner over 1 year ago
- Subject changed from test fails in python_pycairo to [qe-core] test fails in python_pycairo
Updated by openqa_review over 1 year 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/2795207#step/python_pycairo/1
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 szarate over 1 year ago
- Tags set to bugbusters
I'm smelling a change in upstream, looking at the diff, the source file has a tag, which the generated one doesnt... Do we have the same problem for other TW arches what was the previous version of python3-pycairo before sept 30th?
Updated by ggardet_arm over 1 year ago
Both x86_64 and aarch64 are affected: https://openqa.opensuse.org/tests/2859622#step/python_pycairo/15
Updated by ggardet_arm over 1 year ago
Last update of python-pycairo was 2 months ago: https://build.opensuse.org/request/show/1003719
Updated by openqa_review over 1 year 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/2893534#step/ovn/1
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 over 1 year 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/2964674#step/ovn/1
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 dvenkatachala over 1 year ago
- Status changed from New to In Progress
https://openqa.opensuse.org/tests/3030449#step/python_pycairo/15, seeing the differences in the generated SVG file with the expected sample SVG file.
The <g> tag is not present in the test generated svg file.
We can try one of the below steps as a workaround,
- create a new expected SVG file with the latest ciaro and copy it in the data folder, or
- verify only the co-ordinates of generated file instead of comparing files.
Updated by dvenkatachala about 1 year ago
Updated by dvenkatachala about 1 year ago
- Status changed from In Progress to Resolved
Latest run in O3- https://openqa.opensuse.org/tests/3105681