action #50219
closed
[sle][security][sle15sp1] Refine the firefox_nss launch fail and mismatch
Added by bchou about 5 years ago.
Updated almost 5 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP1-Installer-DVD-x86_64-fips_env_tests_crypt_web@64bit fails in
firefox_nss
Test suite description¶
ISO_1=SLE-%VERSION%-Packages-%ARCH%-Build%BUILD%-Media1.iso
Reproducible¶
Fails since (at least) Build 210.1
Expected result¶
Last good: 205.7 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Status changed from New to In Progress
Rewrite as the workaround from x11_start_program launch fail.
From :
x11_start_program('firefox https://html5test.opensuse.org', target_match => 'firefox-html-test', match_timeout => 360);
To :
x11_start_program('firefox', target_match => "firefox-manpage", match_timeout => 360);
send_key "ctrl-t";
wait_still_screen 2;
type_string "https://html5test.opensuse.org";
send_key "ret";
wait_still_screen 2;
assert_screen('firefox-html-test');
The approach can be overcome the x11_start_program try to launch a link https://html5test.opensuse.org fail.
But it will cause the popup warning:
Warning: Unresponsive script (A script on this page may have stopped responding).
It should be the JavaScript problem if it wait for long time to launch a web link, and the network speed is not good, and also it is a random problem while we met in openQA testing.
I try to use the "firefox --safe-mode" to launch the web link, it can overcome the "Warning: Unresponsive script ". But if we start the launch as safe-mode, it is not supported in FIPS mode. the require password didn't show up.
Thus, I plan to start firefox as a general way and report an issue if we met the Warning again.
bchou wrote:
...
It should be the JavaScript problem if it wait for long time to launch a web link, and the network speed is not good, and also it is a random problem while we met in openQA testing.
Have you tried to use other website without javascript for the testing?
I did not check others yet, but I think it will not have problem without javascript.
It could be the javascript problem while running in openQA testing. The problem cannot be reproduced in Manually launch in the physical machine.
- Status changed from In Progress to Resolved
Firefox_NSS random fail issue can be resolved if Add "QEMURAM=2048" into fips_env_tests_crypt_web test to enlarge the VM memories.
https://openqa.suse.de/tests/2896188 (Build 227.1)
Thanks @llzhao's investigation too.
Also available in: Atom
PDF