action #75283: [sle][security][sle15sp3][FIPS][aarch64] test fails in firefox_nss due to password inputfield is not correct addressed - openQA Tests - openSUSE Project Management Tool

Actions

Copy link

action #75283

closed

[sle][security][sle15sp3][FIPS][aarch64] test fails in firefox_nss due to password inputfield is not correct addressed

Added by bchou over 3 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

bchou

Category:

Bugs in existing tests

Target version:

Start date:

2020-10-26

Due date:

% Done:

100%

Estimated time:

20.00 h

Difficulty:

Description

Observation¶

openQA test in scenario sle-15-SP3-Online-aarch64-fips_env_mode_tests_crypt_x11_aarch64@aarch64 fails in
firefox_nss

Test suite description¶

Reproducible¶

Fails since (at least) Build 67.1 (current job)

Expected result¶

Last good: 51.9 (or more recent)

Further details¶

Always latest result in this scenario: latest

Actions

Copy link

Updated by bchou over 3 years ago

Subject changed from [sle][security][sle15sp3][FIPS] test fails in firefox_nss due to password inputfield is not correct addressed to [sle][security][sle15sp3][FIPS][aarch64] test fails in firefox_nss due to password inputfield is not correct addressed

Actions

Copy link

Updated by bchou over 3 years ago

Status changed from New to In Progress

The problem is only reproduced in aarch64 currently, I suspect the error is also a racing condition about poor worker performance in aarch64. I plan to extend the waiting time and also adjust the 2nd firefox launch approach. It could be also some trouble for x11_start_program() if I input 3 parameters under the bad internet connection, thus the input password pop-up window is not reacted before type_string $fips_password.

Actions

Copy link

Updated by rfan1 over 3 years ago

Ben,

How about change the mem size to 4g to see?

Actions

Copy link

Updated by bchou over 3 years ago

Thanks, Richard. It's a good idea, currently, it used 2g, QEMURAM 2048. It is openQA default setting. I think I still need to change the test code to keep away from this issue while the setting is lack of memory. :/

Actions

Copy link