Activity log for bug #1909187

Date Who What changed Old value New value Message
2020-12-24 07:26:20 Po-Hsu Lin bug added bug
2020-12-24 07:26:46 Po-Hsu Lin description Issue found with Focal AWS 5.4.0-1034.35, exclusively on a1.medium startup='Wed Dec 23 18:40:58 2020' tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s perf_event_open02.c:130: TINFO: bench_work estimated loops = 5715 in 500 ms perf_event_open02.c:175: TINFO: [0] value:2287744246 time_enabled:500058840 time_running:500058840 perf_event_open02.c:175: TINFO: [1] value:2287708056 time_enabled:500381232 time_running:500381232 perf_event_open02.c:175: TINFO: [2] value:2289974062 time_enabled:504715896 time_running:504715896 perf_event_open02.c:175: TINFO: [3] value:1715806060 time_enabled:532575876 time_running:399201912 perf_event_open02.c:334: TINFO: nhw: 3, overall task clock: 4233846396 perf_event_open02.c:335: TINFO: hw sum: 54940303470, task clock sum: 12702998172 perf_event_open02.c:347: TINFO: ratio: 3.000345 perf_event_open02.c:349: TFAIL: test failed (ratio was greater than 3) Summary: passed 0 failed 1 broken 0 skipped 0 warnings 0 tag=perf_event_open02 stime=1608748858 dur=9 exit=exited stat=1 core=no cu=881 cs=0 As I can't see this failure on other ARM instances and not on B-5.4 AWS, I won't call this a regression. Issue found with Focal AWS 5.4.0-1034.35, exclusively on a1.medium Fail rate: 2/2 Test failed with:  startup='Wed Dec 23 18:40:58 2020'  tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s  perf_event_open02.c:130: TINFO: bench_work estimated loops = 5715 in 500 ms  perf_event_open02.c:175: TINFO: [0] value:2287744246 time_enabled:500058840 time_running:500058840  perf_event_open02.c:175: TINFO: [1] value:2287708056 time_enabled:500381232 time_running:500381232  perf_event_open02.c:175: TINFO: [2] value:2289974062 time_enabled:504715896 time_running:504715896  perf_event_open02.c:175: TINFO: [3] value:1715806060 time_enabled:532575876 time_running:399201912  perf_event_open02.c:334: TINFO: nhw: 3, overall task clock: 4233846396  perf_event_open02.c:335: TINFO: hw sum: 54940303470, task clock sum: 12702998172  perf_event_open02.c:347: TINFO: ratio: 3.000345  perf_event_open02.c:349: TFAIL: test failed (ratio was greater than 3)  Summary:  passed 0  failed 1  broken 0  skipped 0  warnings 0  tag=perf_event_open02 stime=1608748858 dur=9 exit=exited stat=1 core=no cu=881 cs=0 As I can't see this failure on other ARM instances and not on B-5.4 AWS, I won't call this a regression.
2021-06-21 10:36:57 Krzysztof Kozlowski bug added subscriber Krzysztof Kozlowski
2021-06-21 10:37:31 Krzysztof Kozlowski tags arm64 aws groovy sru-20210531 ubuntu-ltp-syscalls
2021-09-27 05:20:39 Po-Hsu Lin tags arm64 aws groovy sru-20210531 ubuntu-ltp-syscalls 5.11 arm64 aws groovy hirsute sru-20210531 sru-20210906 ubuntu-ltp-syscalls
2021-09-27 05:28:21 Po-Hsu Lin summary perf_event_open02 from ubuntu_ltp_syscalls failed on F-aws a1.medium perf_event_open02 from ubuntu_ltp_syscalls failed on F-aws with instance a1.medium / i3en.24xlarge
2023-03-27 05:24:39 Po-Hsu Lin tags 5.11 arm64 aws groovy hirsute sru-20210531 sru-20210906 ubuntu-ltp-syscalls 5.11 5.4 arm64 aws bionic groovy hirsute oracle sru-20210531 sru-20210906 sru-20230227 ubuntu-ltp-syscalls
2023-03-27 05:25:05 Po-Hsu Lin summary perf_event_open02 from ubuntu_ltp_syscalls failed on F-aws with instance a1.medium / i3en.24xlarge perf_event_open02 from ubuntu_ltp_syscalls failed on F-aws / B-oracle-5.4 with specific instance
2023-07-17 22:45:52 Cory Todd tags 5.11 5.4 arm64 aws bionic groovy hirsute oracle sru-20210531 sru-20210906 sru-20230227 ubuntu-ltp-syscalls 5.11 5.4 arm64 aws bionic groovy hirsute oracle sru-20210531 sru-20210906 sru-20230227 sru-20230710 ubuntu-ltp-syscalls