action #94441
closed[qe-core] Re-schedule pidgin tests
100%
Description
These were disabled due to https://progress.opensuse.org/issues/94177 and blocking many updates.
However, it turns out pidgin is still part of even SLE 15 WE, so it's a good idea to consider fixing the test too.
Acceptance Criteria¶
AC1: Schedule pidgin tests - this time via YAML - on functional + maintenance releases.
AC2: Before enabling, fix any problems that may still remain - likely useful to switch to irc.libera.chat if not yet done.
Updated by tjyrinki_suse over 3 years ago
- Related to action #94177: [qe-core][qem][piglit] test fails in pidgin_IRC: Disconnected, session limit exceeded added
Updated by zluo over 3 years ago
- Category set to Bugs in existing tests
- Assignee set to zluo
- Priority changed from Low to Normal
- Target version set to QE-Core: Ready
let me check this issue at first, the test failed at moment.
Updated by zluo over 3 years ago
https://openqa.suse.de/tests/6226977#step/pidgin_IRC/18 is last successful test run.
Updated by zluo over 3 years ago
https://gitlab.suse.de/openqa/os-autoinst-needles-sles/-/merge_requests/1543 to fix the issue with server freenode.net
Add $SERVERNAME in pidgin for now.
Updated by zluo over 3 years ago
http://10.160.64.152/tests/3322 fixed the issue now for pidgin-IRC.
change yaml schedule and take care for sled, Tumbleweed (add pidgin at first) as well.
for SLED Desktop
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=pidgin_IRC&distri=sle&version=15-SP3&build=187.1&groupid=118#
Updated by zluo over 3 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12864
Will create test suite 'message' and schedule on osd.
Updated by GraceWang over 3 years ago
- Related to action #94288: [desktop] [sle15sp3] Use a YAML file to manage product job group added
Updated by okurz over 3 years ago
This ticket had a due set but exceeded it already by more than 14 days. We would like to take the due date seriously so please update the ticket accordingly (resolve the ticket or update the due-date or remove the due-date). See https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives for details. This update was done as agreed within the SUSE QE Sync call 2021-09-01
Updated by zluo over 3 years ago
https://openqa.opensuse.org/tests/1910362#details:
tests added and scheduled on O3 for Tumbleweed.
Updated by dzedro over 3 years ago
zluo wrote:
https://openqa.opensuse.org/tests/1910362#details:
tests added and scheduled on O3 for Tumbleweed.
And osd ? https://openqa.suse.de/tests/7090559
Updated by zluo over 3 years ago
dzedro wrote:
zluo wrote:
https://openqa.opensuse.org/tests/1910362#details:
tests added and scheduled on O3 for Tumbleweed.
And osd ? https://openqa.suse.de/tests/7090559
There is a couple of message test suite, sorry I forgot yours, Now yaml schedule has been added to it. It should work again.
Updated by zluo over 3 years ago
https://openqa.suse.de/tests/7109129 works fine.
wayland-desktopapps-message@64bit-virtio-vga: https://openqa.suse.de/tests/7126581 some test failed.
x11-desktopapps-message@64bit-2gbram: https://openqa.suse.de/tests/7126568 failed and look it has similar issue as above.
sled 15 sp4 seems to have some problems and it requires some investigations. But they don"t have to do with yaml_schedule which applied on OSD.
Updated by zluo over 3 years ago
- Related to action #98892: [qe-core][sled]test fails in evolution_smoke added
Updated by zluo over 3 years ago
- Related to action #98943: [qe-core][sled]test fails in evolution_mail_imap added
Updated by zluo over 3 years ago
- Related to action #99027: [qe-core][sled]test fails in evolution_meeting_imap added
Updated by zluo over 3 years ago
- Related to action #99087: [qe-core][sled]test fails in thunderbird_pop added
Updated by zluo over 3 years ago
https://openqa.suse.de/tests/7212211 looks much better now. needles got re-created or fixed.
Updated by zluo over 3 years ago
because of issue: https://bugzilla.suse.com/show_bug.cgi?id=1190228
x11-desktopapps-message@64bit-2gbram still failed, this should be fixed in next build. This failure has nothing to do with yaml schedule.
Updated by zluo about 3 years ago
- Status changed from In Progress to Resolved
resolved, yaml schedule is in place already.