action #18242
closed[tools]Fix malbec
0%
Description
Coolo broke it (Seriously, looks like a major FS issue)
Updated by okurz about 7 years ago
- Blocks action #16490: test fail sporadically because of timeout on malbec (ppc64le) added
Updated by RBrownSUSE about 7 years ago
- Status changed from New to Resolved
Fixed, jobs running, tmpfs might need tuning
Updated by nicksinger about 7 years ago
- Project changed from openQA Project to openQA Tests
- Category set to Infrastructure
- Status changed from Resolved to Feedback
https://openqa.suse.de/tests/861383#step/gcc5_Cpp_compilation/19 and https://openqa.suse.de/tests/861383#step/gcc5_fortran_compilation/25 (ENCUNTEED instead of ENCOUNTERED) looks like ninja keys again and also #18400 seems like a malbec issue. Can you please take a look again at that machine?
Updated by nicksinger about 7 years ago
Also this test fails because of "No space left on device": https://openqa.suse.de/tests/861496#
Updated by RBrownSUSE about 7 years ago
disk pool put in place to match the workerconf, missed it first time around, should be fine now
Updated by RBrownSUSE about 7 years ago
- Status changed from Feedback to Resolved
Updated by okurz about 7 years ago
- Status changed from Resolved to Feedback
rbrown: https://openqa.suse.de/tests/867072#step/zypper_lifecycle/6 is "ninja key" on malbec on recent job.
Problem was that the machine "ppc64le-smp" did not have VNC_TYPING_LIMIT=10 set. Changed that now. Let's wait for confirmation.
If that does not help then two options 1) lower typing speed for power from 10 to 7 2) reduce number of workers on malbec
Updated by mgriessmeier about 7 years ago
problems with displaying gnome taskbar and with starting gnome after reboot
https://openqa.suse.de/tests/872345
Updated by RBrownSUSE about 7 years ago
Does not look like an issue in malbec to me
Looks like the test might have rolled back the wrong snapshot
Or something broke in the snapshot parts of the test..why do you think 872345 is related to this poo# besides the fact that it happened to run on malbec?
Updated by RBrownSUSE about 7 years ago
Also, the history of the test shows that it's been broken for some time..I really think we could have an issue either with the test or the product on this architecture.. you need to review this failure and decide where the fault lies, isn't malbec.
Updated by RBrownSUSE about 7 years ago
- Status changed from Feedback to Resolved
typing limit seems to have fixed everything, no sign of new malbec issues, resolving this ticket again
Updated by nicksinger about 7 years ago
- Status changed from Resolved to In Progress
Have to reopen this because of "no space left on device" on malbec again:
https://openqa.suse.de/tests/890944#
Updated by nicksinger about 7 years ago
Here too: https://openqa.suse.de/tests/891061