jjb: Replace open_enoent testcase for a more stable testcase
authorFrancis Deslauriers <francis.deslauriers@efficios.com>
Fri, 17 Feb 2017 16:43:07 +0000 (11:43 -0500)
committerFrancis Deslauriers <francis.deslauriers@efficios.com>
Tue, 28 Feb 2017 19:43:02 +0000 (14:43 -0500)
commit70e85c9830a708869b110e4083ff04fd3bf3cb57
tree9eaf556c832d4945470e5bcfb4059e6e5281c60f
parent64d4186531e1d38372a06e35100a70ea9bb7a7c1
jjb: Replace open_enoent testcase for a more stable testcase

The open_enoent testcase showed a bimodal distribution of time per event
that was measurable even when tracing was disabled. This behaviour was
witnessed only in cases where the open failed with an `enoent` error.
Our investigation of the sys_open code pointed towards to the pathwalk
in the VFS. We decided to simply change the test case to something more
stable due to lack of time to put in the investigation.

Signed-off-by: Francis Deslauriers <francis.deslauriers@efficios.com>
lava/baremetal-tests/failing-open-enoent.yml [deleted file]
lava/baremetal-tests/success-dup-close.yml [new file with mode: 0644]
scripts/lttng-baremetal-tests/lava-submit.py
scripts/lttng-baremetal-tests/run-baremetal-benchmarks.sh
This page took 0.023252 seconds and 4 git commands to generate.