action #157885
closed
[qe-core]test fails in django, need to double confirm with dev if it is a product bug or the package is not ready in BETA phase
Added by rfan1 8 months ago.
Updated 6 months ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP6-Online-x86_64-stack_tests_python@64bit fails in
django
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml.
Reproducible¶
Fails since (at least) Build 54.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Status changed from New to Blocked
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/13958834#step/django/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.
- Status changed from Blocked to Resolved
- Related to action #159972: [qe-core] test fails in django - Django needs to be installed with a compatible version (python311-Django) added
Also available in: Atom
PDF