[yast-devel] How to get info from failed test (old-style)
Hi, I've started getting exit code 16 when running SuSEFirewall test and was not able to find out where the problem is, as logs did not contain anything. I've found out how to run the test manually and get all the logs... This all the info `make check` gives me: Running ./yast2.test/testsuite.exp ... Checking started Running SuSEFirewall ... FAIL: Test case failed for SuSEFirewall: Return code: '16'. child process exited abnormally And here's what I needed to run to get all the logs: `cd yast-yast2/library/network/testsuite` `/usr/lib/YaST2/bin/y2base -l - -c /usr/share/YaST2/data/testsuite/log.conf -I ../src -M ../src tests/SuSEFirewall.rb UI` Then I've got everything including the error and its backtrace Client call failed with 'undefined method `[]' for nil:NilClass' and backtrace ["/usr/share/YaST2/lib/yast2/systemd_unit.rb:143:in `block in extract_properties'", ...] Internal error. Please report a bug report with logs. Details: undefined method `[]' for nil:NilClass Caller: /usr/share/YaST2/lib/yast2/systemd_unit.rb:143:in `block in extract_properties' I hope this will be helpful Thanks to Josef for hints Bye Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 27.3.2014 09:33, Lukas Ocilka wrote:
And here's what I needed to run to get all the logs: `cd yast-yast2/library/network/testsuite` `/usr/lib/YaST2/bin/y2base -l - -c /usr/share/YaST2/data/testsuite/log.conf -I ../src -M ../src tests/SuSEFirewall.rb UI`
You might also need to set Y2ALLGLOBAL=1 while running a testsuite (if it calls private methods/variables), so... Y2ALLGLOBAL=1 /usr/lib/YaST2/bin/y2base -l - -c /usr/share/YaST2/data/testsuite/log.conf -I ../src -M ../src tests/SuSEFirewall.rb UI Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
And here's what I needed to run to get all the logs: `cd yast-yast2/library/network/testsuite` `/usr/lib/YaST2/bin/y2base -l - -c /usr/share/YaST2/data/testsuite/log.conf -I ../src -M ../src tests/SuSEFirewall.rb UI`
You might also need to set Y2ALLGLOBAL=1 while running a testsuite (if it calls private methods/variables), so...
does it work for ruby code? Anyway, AFAIK old testsuite sets it automatically.
Michak -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Mon, 31 Mar 2014 15:34:17 +0200 "Michal Filka" <michal.filka@suse.cz> wrote:
And here's what I needed to run to get all the logs: `cd yast-yast2/library/network/testsuite` `/usr/lib/YaST2/bin/y2base -l - -c /usr/share/YaST2/data/testsuite/log.conf -I ../src -M ../src tests/SuSEFirewall.rb UI`
You might also need to set Y2ALLGLOBAL=1 while running a testsuite (if it calls private methods/variables), so...
does it work for ruby code? Anyway, AFAIK old testsuite sets it automatically.
Michak
Michal, as Lukas wrote above it is way how to run old testsuite directly with one test to get all logs (so it is not set with runtest.sh), which is helpful to debug it. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Josef Reidinger
-
Lukas Ocilka
-
Michal Filka