<div dir="ltr"><div>I have traced the failing tests to missing supplementary shell scripts that apparently are newly added, and weren't packaged to the target.</div><div><br></div><div>Also, /tmp indeed wasn't big enough.<br></div><div><br></div><div>With those issues addressed (patch is coming), I am still having two failures:</div><div><br></div><div># Failed test (../../../../../lttng-tools-2.11.0/tests/regression/tools/live/live_test.c:main() at line 707)<br># Got first packet index with offset 0 and len 4096<br>not ok 6 - Get metadata, received 0 bytes<br>FAIL: tools/live/test_ust_tracefile_count 6 - Get metadata, received 0 bytes<br></div><div><br></div><div># Got first packet index with offset 0 and len 4096<br>not ok 6 - Get metadata, received 0 bytes<br>FAIL: tools/live/test_ust 6 - Get metadata, received 0 bytes<br></div><div><br></div><div>What's weird is that sometimes they pass. Could there be a race or some timing issue in the test?<br></div><div><br></div><div>Alex<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 20 Jan 2020 at 18:37, Jonathan Rajotte-Julien <<a href="mailto:jonathan.rajotte-julien@efficios.com" target="_blank">jonathan.rajotte-julien@efficios.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Could you point me toward reports for the failing tests?<br>
<br>
I just want to make sure they are not actual regression.<br>
<br>
A yocto specific patch was dropped that allowed ptest to pass when<br>
lttng-ust is not present. This can be a source of problems.<br>
OE commit:015aea5d93614676decd18578a8ae2d68417cfc5<br>
<br>
Also some tests required a minimum requirement for /tmp that could lead to<br>
problem for image/test setup with limited memory since AFAIK /tmp size is<br>
derived from the available memory (at least when using qemu test image).<br>
<br>
Cheers<br>
<br>
On Mon, Jan 20, 2020 at 06:24:56PM +0100, Alexander Kanavin wrote:<br>
> These tests are producing failures that appear and<br>
> disappear randomly. This requires investigation<br>
> by someone with expertise, so let's disable until then.<br>
> <br>
> Signed-off-by: Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>><br>
> ---<br>
> meta/conf/distro/include/ptest-packagelists.inc | 2 +-<br>
> 1 file changed, 1 insertion(+), 1 deletion(-)<br>
> <br>
> diff --git a/meta/conf/distro/include/ptest-packagelists.inc b/meta/conf/distro/include/ptest-packagelists.inc<br>
> index 49cb9046c6c..f42e90bd187 100644<br>
> --- a/meta/conf/distro/include/ptest-packagelists.inc<br>
> +++ b/meta/conf/distro/include/ptest-packagelists.inc<br>
> @@ -58,6 +58,7 @@ PTESTS_FAST = "\<br>
> # rt-tests-ptest \ # Needs to be checked whether it runs at all<br>
> # bash-ptest \ # Test outcomes are non-deterministic by design<br>
> # mdadm-ptest \ # Multiple failures; mdmon crashes in at least one of the tests<br>
> +# lttng-tools-ptest \ # Random failures that are difficult to reproduce<br>
> #"<br>
> <br>
> PTESTS_SLOW = "\<br>
> @@ -67,7 +68,6 @@ PTESTS_SLOW = "\<br>
> glib-2.0-ptest \<br>
> gstreamer1.0-ptest \<br>
> libevent-ptest \<br>
> - lttng-tools-ptest \<br>
> openssh-ptest \<br>
> openssl-ptest \<br>
> perl-ptest \<br>
> -- <br>
> 2.17.1<br>
> <br>
> -- <br>
> _______________________________________________<br>
> Openembedded-core mailing list<br>
> <a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
<br>
-- <br>
Jonathan Rajotte-Julien<br>
EfficiOS<br>
</blockquote></div></div>