action #120984
closed
assert_script_sudo does not see result
Added by dimstar over 1 year ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
Description
Observation¶
According to the screen shots, pidgin is properly removed, zypper returns code 0
All seems fine, yet the test fails
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-message-gnome@64bit fails in
clean_pidgin
Test suite description¶
Reproducible¶
Fails since (at least) Build 20221125
Expected result¶
Last good: 20221124 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from test fails in clean_pidgin to assert_script_sudo does not see result
- Priority changed from Normal to Urgent
- Subject changed from assert_script_sudo does not see result to [desktop] assert_script_sudo does not see result
- Subject changed from [desktop] assert_script_sudo does not see result to assert_script_sudo does not see result
Based on above comments and discussion in eng-testing slack channel on Monday between Dominique and Oliver, this ticket doesn't belong to [Desktop]. So remove the [Desktop] from subject.
- Assignee set to ybonatakis
- Status changed from New to In Progress
The problem is some confusing implementation and how the script_sudo and assert_script_sudo work with the marker. From the os-autoinst-distri-opensuse side the only problem is that the assert_script_sudo uses wrong argument[0]. However the fix requires the necessary bits on os-autoinst. PR in the way
[0] https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16002
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF