action #49865
closed[opensuse] Typing too fast in gcc_fortran_compilation and gcc_compilation on aarch64
Added by ggardet_arm about 5 years ago. Updated over 4 years ago.
0%
Description
Observation¶
Typing too fast in gcc_fortran_compilation and gcc_compilation on aarch64 at wget stage.
Reproducible¶
Fails since Build 430.1
in scenario opensuse-15.1-DVD-aarch64-Build430.1-toolchain_zypper@aarch64
Expected result¶
Last good: ggardet_test_zypper_toolchain_aarch64
Further details¶
Always latest result in this scenario: latest
Updated by ggardet_arm about 5 years ago
- Subject changed from Typing too fast in gcc_fortran_compilation and gcc_compilation fails on aarch64 to Typing too fast in gcc_fortran_compilation and gcc_compilation on aarch64
Updated by SLindoMansilla about 5 years ago
- Subject changed from Typing too fast in gcc_fortran_compilation and gcc_compilation on aarch64 to [functional][u] Typing too fast in gcc_fortran_compilation and gcc_compilation on aarch64
- Description updated (diff)
- Priority changed from Normal to High
Updated by okurz about 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/907759
Updated by ggardet_arm about 5 years ago
- Status changed from New to Feedback
- Assignee set to ggardet_arm
Setting VNC_TYPING_LIMIT to 7 instead of 10 fixed it: https://openqa.opensuse.org/tests/910100
As sometimes, some other tests fail with missed keys I set VNC_TYPING_LIMIT=7 for @aarch64 machine. It will slow down tests, but they will be more reliable, which will avoid tests restarts.
Let's see if it is fixed for next TW snapshot, and for current Leap 15.1 snapshot: https://openqa.opensuse.org/tests/910602
Updated by ggardet_arm about 5 years ago
- Status changed from Feedback to Resolved
Updated by SLindoMansilla about 5 years ago
- Subject changed from [functional][u] Typing too fast in gcc_fortran_compilation and gcc_compilation on aarch64 to [opensuse] Typing too fast in gcc_fortran_compilation and gcc_compilation on aarch64
Updated by okurz almost 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/933790
Updated by okurz almost 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/967612
Updated by okurz almost 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/967612
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/1004833
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/1017809
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/1053675
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/1066195
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz over 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: toolchain_zypper
https://openqa.opensuse.org/tests/1081633
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed