-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Analyze the rt-tests results and fix issues #439
Comments
The priority of 96 if passed to rt-migrate causes failure. The test isn't designed well to handle high priority of 96. The test takes this priority and adds the count of number of tasks which becomes greater than 99. The 99 is the highest priority level for SCHED_FIFO. Hence, the priority setting of the main thread fails, we get warning and later test failure: Warning, can't set priority of main thread! Instead of fixing the test at this time, let's use priority of 90 instead of 96 such that the total priority of main thread remains below highest priority level. We can set any other lower priority than 90 here as well such as 51 which is set in the rt-migrate-test.sh by default. Relates kernelci/kernelci-project#439 Signed-off-by: Muhammad Usama Anjum <[email protected]>
When MLOCKALL is set to 'true', the lava job has MLOCKALL becomes true [1] which in turn translates to "True" while job execution [2]. It causes error as the test expects true instead of True. ./pi-stress.sh -D 60s -m True -r false -w hackbench ./pi-stress.sh: 37: True: not found Fix it by using double quotes instead. [1] https://lava.collabora.dev/scheduler/job/15562666/definition#defline43 [2] https://lava.collabora.dev/scheduler/job/15562666#L220 Relates kernelci/kernelci-project#439 Signed-off-by: Muhammad Usama Anjum <[email protected]>
Add missing configurations needed to run rtla timerlat and osnoise tests. Relates kernelci/kernelci-project#439 Signed-off-by: Muhammad Usama Anjum <[email protected]>
Opened separate ticket for bug in test-definition scripts: Linaro/test-definitions#530 |
Add missing configurations needed to run rtla timerlat and osnoise tests. Relates kernelci/kernelci-project#439 Signed-off-by: Muhammad Usama Anjum <[email protected]>
The priority of 96 if passed to rt-migrate causes failure. The test isn't designed well to handle high priority of 96. The test takes this priority and adds the count of number of tasks which becomes greater than 99. The 99 is the highest priority level for SCHED_FIFO. Hence, the priority setting of the main thread fails, we get warning and later test failure: Warning, can't set priority of main thread! Instead of fixing the test at this time, let's use priority of 90 instead of 96 such that the total priority of main thread remains below highest priority level. We can set any other lower priority than 90 here as well such as 51 which is set in the rt-migrate-test.sh by default. Relates kernelci/kernelci-project#439 Signed-off-by: Muhammad Usama Anjum <[email protected]>
Add missing configurations needed to run rtla timerlat and osnoise tests. Relates kernelci/kernelci-project#439 Signed-off-by: Muhammad Usama Anjum <[email protected]>
Add missing configurations needed to run rtla timerlat and osnoise tests. Relates kernelci/kernelci-project#439 Signed-off-by: Muhammad Usama Anjum <[email protected]>
When MLOCKALL is set to 'true', the lava job has MLOCKALL becomes true [1] which in turn translates to "True" while job execution [2]. It causes error as the test expects true instead of True. ./pi-stress.sh -D 60s -m True -r false -w hackbench ./pi-stress.sh: 37: True: not found Fix it by using double quotes inside single quotes. - First set of quotations allows Jinja template engine to treat it as a string - Second set is for LAVA to also treat is as string and prevent YAML parser from making it a bool [3] is successful job after this change. [1] https://lava.collabora.dev/scheduler/job/15562666/definition#defline43 [2] https://lava.collabora.dev/scheduler/job/15562666#L220 [3] https://lava.collabora.dev/scheduler/job/15790058 Relates kernelci/kernelci-project#439 Co-authored-by: Paweł Wieczorek <[email protected]> Signed-off-by: Muhammad Usama Anjum <[email protected]>
When MLOCKALL is set to 'true', the lava job has MLOCKALL becomes true [1] which in turn translates to "True" while job execution [2]. It causes error as the test expects true instead of True. ./pi-stress.sh -D 60s -m True -r false -w hackbench ./pi-stress.sh: 37: True: not found Fix it by using double quotes inside single quotes. - First set of quotations allows Jinja template engine to treat it as a string - Second set is for LAVA to also treat is as string and prevent YAML parser from making it a bool [3] is successful job after this change. [1] https://lava.collabora.dev/scheduler/job/15562666/definition#defline43 [2] https://lava.collabora.dev/scheduler/job/15562666#L220 [3] https://lava.collabora.dev/scheduler/job/15790058 Relates kernelci/kernelci-project#439 Co-authored-by: Paweł Wieczorek <[email protected]> Signed-off-by: Muhammad Usama Anjum <[email protected]>
Adjust the timeout: kernelci/kernelci-core#2696 |
I'm checking the results after merging Linaro/test-definitions#530. We use https://github.com/kernelci/test-definitions in our jobs. I don't know why we have forked the original repository. I'll ask around and get the fork updated and re-run to get the latest results. |
I ran all tests on the stable-rt v6.6-rt branch and all tests are passing. (Convert above file to html and view for results) We use rtla package from debian respository to run 2 tests (osnoise and timerlat). This tools is present in the mainline (tools/tracing/rtla). We should install the latest tool from mainline instead of installing from debian package. Because of old package, these tests are partially run. I'll create a separate ticket for this. |
Failures:
Related to: #417
The text was updated successfully, but these errors were encountered: