<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta-selftest, branch 2.4_M1</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=2.4_M1</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=2.4_M1'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2017-06-12T14:08:30+00:00</updated>
<entry>
<title>meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.conf</title>
<updated>2017-06-12T14:08:30+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2017-06-07T09:20:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f6f2034526009d21036bfc42326f7d883e84b1cb'/>
<id>urn:sha1:f6f2034526009d21036bfc42326f7d883e84b1cb</id>
<content type='text'>
This means mismatched layers are more clearly identified to the user in
cases where compatibility has not been tested. This is perhaps not as
needed for the core repository (other than CORENAMES) but lets lead by
example.

(From OE-Core rev: cde66d5eac8e5c2821ba225dc4be4af4e0581652)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runtime-test.py: Split different tests inside selftest.py</title>
<updated>2017-06-09T16:12:13+00:00</updated>
<author>
<name>Humberto Ibarra</name>
<email>humberto.ibarra.lopez@intel.com</email>
</author>
<published>2017-06-05T17:19:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f1812e090b32f8c1bb33e4f26a246e5fb5e49c13'/>
<id>urn:sha1:f1812e090b32f8c1bb33e4f26a246e5fb5e49c13</id>
<content type='text'>
There were two completely different tests inside selftest.py,
and the only reason for them to be together was that both needed
the same mechanism to execute (run testimage from within selftest)

This fixes the design issue and error-prone situation by separating
these tests. In add a new module for dnf-runtime and also has an
extra time added to running the tests, but it is minimal since
the builds reuse data from previuous build.

[YOCTO #11436]

(From OE-Core rev: 2f6a506018973f0eaf1306555df3e74a3ab25680)

Signed-off-by: Humberto Ibarra &lt;humberto.ibarra.lopez@intel.com&gt;
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>wic-image-minimal: stop using core-image-minimal</title>
<updated>2017-04-12T14:09:58+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2017-04-11T18:11:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=64a379b3255929864164eb2a7fe792faf07c06ad'/>
<id>urn:sha1:64a379b3255929864164eb2a7fe792faf07c06ad</id>
<content type='text'>
Removed dependency to core-image-minimal rootfs from the
recipe and .wks file. This was a bad idea as recipes are
not allowed to use other recipe's rootfs or anything else
from workdir.

This should also fix test_qemu test case when rm_work is
enabled.

(From OE-Core rev: 0f1879982ab6006f14ac2c9f5546a7b1f79460cd)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>wic-image-minimal.wks: vda -&gt; sda</title>
<updated>2017-04-12T14:09:57+00:00</updated>
<author>
<name>Robert Yang</name>
<email>liezhi.yang@windriver.com</email>
</author>
<published>2017-04-11T09:21:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d538cbb95e76991fa916d9b22b5a3d2fdd5ff796'/>
<id>urn:sha1:d538cbb95e76991fa916d9b22b5a3d2fdd5ff796</id>
<content type='text'>
Previously, runqemu grep root=/dev/sd or root=/dev/hd on the image, and
would use vda if no grep result, now we have set QB_DRIVE_TYPE to
"/dev/sd" by default, and the device will be /dev/sda, so use sda to
replace vda in the test case.

(From OE-Core rev: aa8df7e17bb4bb0a92938cbc36cd8b22bcf14cfa)

Signed-off-by: Robert Yang &lt;liezhi.yang@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>oe-selftest: test wic rawcopy plugin</title>
<updated>2017-03-23T13:19:49+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2017-03-22T13:42:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d2e02098669a43bf6fc61a963850c276d6884fce'/>
<id>urn:sha1:d2e02098669a43bf6fc61a963850c276d6884fce</id>
<content type='text'>
Added test_rawcopy_plugin_qemu test case and wks template.

This test builds ext4 rootfs image, copies it to the root
partition of the wic image using rawcopy plugin and
boots wic image in qemu.

[YOCTO #10618]

(From OE-Core rev: db1f511228e26aaeeff452427637942747bbf42b)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>selftest: wictestdisk: machine agnostic WKS for use with selftest</title>
<updated>2017-03-22T11:35:22+00:00</updated>
<author>
<name>Maciej Borzecki</name>
<email>maciej.borzecki@rndity.com</email>
</author>
<published>2017-03-21T11:35:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=74c65b7528c8cb07f96dafcb75e52d171ad68a39'/>
<id>urn:sha1:74c65b7528c8cb07f96dafcb75e52d171ad68a39</id>
<content type='text'>
Add a kickstart for an image that is not limited to use on x86 compatible
machines. This allows us to run more wic tests on non-x86 architectures.

(From OE-Core rev: c722569a8b136ffbbe4d2723bbc50fc3ae5aed42)

Signed-off-by: Maciej Borzecki &lt;maciej.borzecki@rndity.com&gt;
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>rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable</title>
<updated>2017-03-17T16:53:04+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alexander.kanavin@linux.intel.com</email>
</author>
<published>2017-03-16T13:19:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2b77735c72cb5100dbd850e79d4f639e82629842'/>
<id>urn:sha1:2b77735c72cb5100dbd850e79d4f639e82629842</id>
<content type='text'>
I've used a previous patch (which was never merged) by
Humberto Ibarra &lt;humberto.ibarra.lopez@intel.com&gt; as a model
for how to do runtime testing of this feature (e.g. we need to boot
an image, run dnf on it, and check that it is indeed able to
access the remote repo over http). Here's his original commit message:

=====
Testing that feeds specified with PACKAGE_FEED_URIS var are set
correctly has two parts. First a build with this var set is required,
and then smart update needs to be issued in the running taget.

The previous is not a common selftest practice because this is a
simple test, but requires building and running a specific image,
which takes a lot of time. testimage is not a good fit either,
since the images tested there do not have the PACKAGE_FEED_URIS
var set.

For this test, the runtime-test module is being used, which is a
selftest module but runs a testimage command. The var and test
environment were set in runtime-perf.py and the actual test is
done in a new testcase added to meta-selftest layer.
=====

[YOCTO #10872]

(From OE-Core rev: 3a9e2fdef9316e24b52ce99ac355fc2b09786c72)

Signed-off-by: Alexander Kanavin &lt;alexander.kanavin@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>run-postinsts: simplify the logic of whether to install it to images</title>
<updated>2017-03-14T14:42:17+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alexander.kanavin@linux.intel.com</email>
</author>
<published>2017-02-17T16:47:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=529244ee212fe14019e35a5f163fab705ddbf141'/>
<id>urn:sha1:529244ee212fe14019e35a5f163fab705ddbf141</id>
<content type='text'>
The logic is scattered all over the place, but amounts to
"install, unless the rootfs is read only". Let's express that directly.

(From OE-Core rev: 697804229a172125ce7d3bfc9b343812d6fe3240)

Signed-off-by: Alexander Kanavin &lt;alexander.kanavin@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-selftest: add selftest-ed recipes</title>
<updated>2017-03-10T14:50:10+00:00</updated>
<author>
<name>Joshua Lock</name>
<email>joshua.g.lock@intel.com</email>
</author>
<published>2017-03-08T17:24:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=52c10b6e58adbdd8489ec2e491d742d942e0c53f'/>
<id>urn:sha1:52c10b6e58adbdd8489ec2e491d742d942e0c53f</id>
<content type='text'>
The oe-selftest oescripts.TestScripts.test_cleanup_workdir was using
gzip and the GPLv2 variant to test cleanup of the workdir. This broke
with the removal of GPLv2 recipes from OE-Core.

Instead of relying on recipes in OE-Core remaining static we should
ensure that meta-selftest provides recipes required for the tests to pass.
To that end we take a copy of the current GPLv2 and GPLv3 variants of ed
and include them in meta-selftest as new recipes.
We chose ed over gzip as gzip has dependencies which would require
additional GPLv2 recipes to be included in meta-selftest.

(From OE-Core rev: 2ac83239698c403bb575e6c5b19f19fcffa389ed)

Signed-off-by: Joshua Lock &lt;joshua.g.lock@intel.com&gt;
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>wic: add WKS_FILE_DEPENDS variable</title>
<updated>2017-03-04T23:18:18+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2017-02-21T15:09:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ee860b3bf5117ef4b01530d336dd9c4e0d7b5550'/>
<id>urn:sha1:ee860b3bf5117ef4b01530d336dd9c4e0d7b5550</id>
<content type='text'>
This variable should be used to specify dependencies that
will be added to DEPENDS only if wic image build is 'active'
i.e. when 'wic' is in IMAGE_FSTYPES.

(From OE-Core rev: 243ccd6b8b389231f6c4a8e251c2bd6b2cf6eaad)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
