<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/lib/oeqa/runtime/cases/ptest.py, branch scarthgap</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=scarthgap</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=scarthgap'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2023-09-18T07:53:10+00:00</updated>
<entry>
<title>ptest: report tests that were killed on timeout</title>
<updated>2023-09-18T07:53:10+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2023-09-17T09:38:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4d1461595a3494864dd98e41c2501db7c3690ae5'/>
<id>urn:sha1:4d1461595a3494864dd98e41c2501db7c3690ae5</id>
<content type='text'>
I'm not sure if this was reported correctly before, but it
currently is not. Test that is stuck is an error in itself.

(From OE-Core rev: 002e27c9932a83e46be0b03a5232594cfba7212c)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oeqa/runtime/ptest: Make returning no test results a failure</title>
<updated>2023-05-03T06:33:18+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2023-04-28T16:51:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5caf9e375fcb9793e50772e590de1e137d3887f9'/>
<id>urn:sha1:5caf9e375fcb9793e50772e590de1e137d3887f9</id>
<content type='text'>
Ensure that even if a ptests results section is empty, the log parser adds that
empty section. Then ensure that empty sections trigger warnings.

This means if a ptest suddently stops returning any results, we notice and see
warnings about it. This has gone unnoticed on the autobuilder far too many times
so is very much worth highlighting as a regression. We shouldn't have empty ptests.

(From OE-Core rev: 5ad0cf57b41ec7f44647a03bc568d0b24906cc8d)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>lib: Add copyright statements to files without one</title>
<updated>2022-08-12T11:00:43+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-08-10T19:40:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ce08cf4825f0e4e42509794a2dcd53a3ea5126e4'/>
<id>urn:sha1:ce08cf4825f0e4e42509794a2dcd53a3ea5126e4</id>
<content type='text'>
Where there isn't a copyright statement, add one to make it explicit.
Also add license identifiers as MIT if there isn't one.

(From OE-Core rev: bb731d1f3d2a1d50ec0aed864dbca54cf795b040)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oeqa/runtime/cases/ptest: Increase test timeout from 300s to 450s</title>
<updated>2021-08-06T05:34:58+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2021-06-02T21:46:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=45632b5366da88673715ba007be7c0c3739b09a9'/>
<id>urn:sha1:45632b5366da88673715ba007be7c0c3739b09a9</id>
<content type='text'>
Some tests such as lttng-tools are marginal and timing out on the autobuilder
with the current 300s default. Increase to avoid this noise in the ptest
failures list.

(From OE-Core rev: 5fb902a52e35130af6b0735a087c709daa35655f)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oeqa/ptest: print a warning if ptests failed</title>
<updated>2021-01-20T00:45:05+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-12-19T17:29:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0955777d5fdd9cbfae87e2a1695c611624afe717'/>
<id>urn:sha1:0955777d5fdd9cbfae87e2a1695c611624afe717</id>
<content type='text'>
This allows spotting ptest regressions without having hard ptest failures
(for that full ptest stability should be achieved).

(From OE-Core rev: 79b54d902df2788b0822b6c9cc14705ab00e6a5b)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oeqa/runtime/cases/ptest: Make output content path absolute</title>
<updated>2020-06-23T11:31:03+00:00</updated>
<author>
<name>Andrej Valek</name>
<email>andrej.valek@siemens.com</email>
</author>
<published>2020-06-22T17:33:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=cea56554d0a52bedc2f871d43b509294de0b5a15'/>
<id>urn:sha1:cea56554d0a52bedc2f871d43b509294de0b5a15</id>
<content type='text'>
The output content is created in current directory, because json content
has no defined absolute path to WORKDIR as in bitbake.

(From OE-Core rev: 14203b2cb9aa62f55cb12230ac8012b3cd995be7)

Signed-off-by: Andrej Valek &lt;andrej.valek@siemens.com&gt;
Signed-off-by: Peter Marko &lt;peter.marko@siemens.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oeqa/runtime: Use libdir to run ptest-runner</title>
<updated>2020-05-02T08:08:53+00:00</updated>
<author>
<name>Anibal Limon</name>
<email>anibal.limon@linaro.org</email>
</author>
<published>2020-04-28T21:18:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=81b8656f6beae97fb1f4a99b1d92f71077c716e1'/>
<id>urn:sha1:81b8656f6beae97fb1f4a99b1d92f71077c716e1</id>
<content type='text'>
In multilib build configs libs can be installed in /usr/lib{32,64,x32}
so use libdir to specify the correct ptest directory along with default
/usr/lib.

[YOCTO #12604]

(From OE-Core rev: e44ca998c27f494466a524d09f751f963ec9be20)

Signed-off-by: Aníbal Limón &lt;anibal.limon@linaro.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oeqa-runtime: add missing import os to ptest case</title>
<updated>2020-03-06T08:19:18+00:00</updated>
<author>
<name>Stefan Kral</name>
<email>sk@typedivision.de</email>
</author>
<published>2020-03-05T19:30:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=56bbdd33d8c58376d3a1e11785581f67d6ecd98f'/>
<id>urn:sha1:56bbdd33d8c58376d3a1e11785581f67d6ecd98f</id>
<content type='text'>
Add missing import os statement to the oeqa runtime ptest.py

(From OE-Core rev: e41c92c60694052c8292c1ea6b3d0b427aafafd7)

Signed-off-by: Stefan Kral &lt;sk@typedivision.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ptest: add an option to enforce a failure (e.g. ptests are required to pass)</title>
<updated>2020-02-25T10:41:22+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-02-23T13:52:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c43423cd28d086d31c06c7e047dba139b35f5cdb'/>
<id>urn:sha1:c43423cd28d086d31c06c7e047dba139b35f5cdb</id>
<content type='text'>
This can be useful with a more specific, targeted and robust set of ptest
packages; the benefit is that ptest regressions are caught as they happen
and can be more easily traced to changes that caused them.

The existing AB ptest image continues to be expected to fail, my observation
of the AB runs is that the full set of ptests is not robust enough
(particularly around socket/network related tests) and sporadically fails
in random places. This can probably be addressed by making ptests exclusive
to a worker (e.g. there is no other workload happening at the same time as
ptests).

(From OE-Core rev: 102afcc7ea7d7673183f272a29ab233084ad168b)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ptest: report ptests that couldn't be run at all</title>
<updated>2020-01-10T21:18:21+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-01-08T13:27:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=544cad3791c0cab59163fc662641ba263ea8c311'/>
<id>urn:sha1:544cad3791c0cab59163fc662641ba263ea8c311</id>
<content type='text'>
Currently if a ptest does not produce PASS or FAIL, but simply
errors out, this is not caught or reported; I think some ptests
may have silently regressed due to this.

(From OE-Core rev: 4b78b6571a3653d7d8e9dab9512bad5d39483988)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
