<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-sato/images, branch dunfell-23.0.4</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=dunfell-23.0.4</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=dunfell-23.0.4'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2020-03-24T16:39:40+00:00</updated>
<entry>
<title>core-image-sato-ptest-fast: don't hard fail in ptests</title>
<updated>2020-03-24T16:39:40+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-03-22T11:39:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6c58c34a44d7ee37ac20f5b8d70b52af65af7fd1'/>
<id>urn:sha1:6c58c34a44d7ee37ac20f5b8d70b52af65af7fd1</id>
<content type='text'>
Unfortunately, a couple of tests sporadically fail still;
bugs have been filed, but they will take time to resolve.

(From OE-Core rev: 6b408f40b6c214d05433c41f0cd6200c715cc615)

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: 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>core-image-sato-sdk-ptest: do not pull in ptest-pkgs</title>
<updated>2020-02-21T17:48:09+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-02-19T19:47:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8b7523f13ea0ebb86fdcbc3b5d39408c1f6d45ef'/>
<id>urn:sha1:8b7523f13ea0ebb86fdcbc3b5d39408c1f6d45ef</id>
<content type='text'>
The lists of ptests are defined via PTESTS_FAST and PTESTS_SLOW;
specifying 'ptests-pkgs' also pulls in additional ptests that
are specifically excluded from those lists due to causing issues with
ptesting. (particularly bash-ptest is one such item)

(From OE-Core rev: 1d8e5d1bc1aa8fdaf967395e27b13cc989717fb7)

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>core-image-sato-sdk-ptest: use 2G of RAM</title>
<updated>2020-01-28T11:11:20+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2020-01-27T14:19:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=dd3e190fca76a28f7ffe4bfeed0d6d7654d0093f'/>
<id>urn:sha1:dd3e190fca76a28f7ffe4bfeed0d6d7654d0093f</id>
<content type='text'>
Particularly, 1G wasn't enough for lttng-tools ptests as
half of that went to /tmp, and lttng-tools needs more.

(From OE-Core rev: abc308a38c6e37afcaf507858a6578c10438c5d8)

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>core-image-sato: don't use 512MB in qemumips</title>
<updated>2019-09-06T07:15:45+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2019-09-05T15:56:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4738a499ae7f989459f9cf4be55185f896059320'/>
<id>urn:sha1:4738a499ae7f989459f9cf4be55185f896059320</id>
<content type='text'>
qemumips doesn't appear to work well with 512MB of RAM and randomly hangs.  As
the bump to 512MB was primarily motivated by the memory needs of virtualised GL
which doesn't work in qemumips currently, drop the memory back to 256MB for
qemumips.

(From OE-Core rev: 499a31cf06c934b40b5866d5eb77c9ad20c9a15f)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>images: use 512M of RAM in qemu if 'opengl" is in DISTRO_FEATURES</title>
<updated>2019-08-28T10:31:21+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2019-08-20T15:32:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3f5c70649a9aaa13ef755ea57576d2bd6d9d2e60'/>
<id>urn:sha1:3f5c70649a9aaa13ef755ea57576d2bd6d9d2e60</id>
<content type='text'>
256M was found to be no longer sufficient, as the X server fails to
start with the modesetting driver and 3D enabled.

Only images that actually include X11 are adjusted.

(From OE-Core rev: 9dd0812acc73287287b48d28e0935baf7f545b58)

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>core-image-sato-sdk-ptest: Reduce image padding size due to bootimg 4GB limit</title>
<updated>2019-07-09T22:30:44+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-07-06T16:46:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9437010a630b7fefbcf1dea00f3d23ab0e6556b2'/>
<id>urn:sha1:9437010a630b7fefbcf1dea00f3d23ab0e6556b2</id>
<content type='text'>
This image continues to run out of space on the autobuilder, tweak it a bit
further now the image space requirements were reduced after various ptest
fixes to avoid the error.

(From OE-Core rev: 9f974dd51c18a1387134a9350097dea97ef5f7d0)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>core-image-sato-sdk-ptest: Tweak size to stay within 4GB limit</title>
<updated>2019-05-15T16:53:29+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-05-15T14:45:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f8f972c072b2e8bc36e4049187a37c50190e42f2'/>
<id>urn:sha1:f8f972c072b2e8bc36e4049187a37c50190e42f2</id>
<content type='text'>
Adding the valgrind debug symbol information caused the genericx86-64 image to
overflow the 4GB boundary. Tweak the sizes to avoid autobuilder failures yet
leave enough space all the tests still run successfully.

(From OE-Core rev: fa24a5056acea6610e2ad1a1eb1e7425a3828979)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>core-image-sato-sdk-ptest: Add temporary PROVIDES core-image-sato-ptest</title>
<updated>2019-04-23T22:30:19+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-04-17T16:03:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8a781a727e08763244f97357680aebbf9a3eb911'/>
<id>urn:sha1:8a781a727e08763244f97357680aebbf9a3eb911</id>
<content type='text'>
Since we want to ultimately move this recipe to that name, add a PROVIDES
to allow things to work whilst we fix the bugs preventing the move. This
avoids having to keep changing the autobuilder.

(From OE-Core rev: 2b70ea6ca2c96fb233f42cfe5058cc89c9de5f82)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>core-image-sato-sdk-ptest: Include more ptests in ptest image</title>
<updated>2019-04-23T22:30:19+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2019-04-17T13:21:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=be957ad7b4e200d3091e1a749e6904e72dc1a1e7'/>
<id>urn:sha1:be957ad7b4e200d3091e1a749e6904e72dc1a1e7</id>
<content type='text'>
There are recipes not included in core-image-sato-sdk which have ptests, include
these in our ptest test image using the new include file.

(From OE-Core rev: f685ec5740e1a8c3922f8f0631ddaed4b2a5d1f0)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
