diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-04-20 17:19:11 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-04-26 14:00:50 +0100 |
commit | f135cb36596d9cc8996277f49b296b9f73b76b73 (patch) | |
tree | b50117e2cc4115cdc0c62c0b7137e2edf72a2bce /meta/lib/oeqa/selftest/cases/sysroot.py | |
parent | d645fe38d38a9fe499c2c79b1b2dced3bed01a89 (diff) | |
download | poky-f135cb36596d9cc8996277f49b296b9f73b76b73.tar.gz |
oeqa/selftest: Add test for conflicting sysroot provider
sysroot-test depends on virtual/sysroot-test which we build for one machine,
switch machine, switch provider of virtual/sysroot-test and check that the
sysroot is correctly cleaned up. The files in the two providers overlap
so can cause errors if the sysroot code doesn't function correctly.
Yes, sysroot-test should be machine specific really to avoid this, however
the sysroot cleanup should also work.
This adds a test for bug:
[YOCTO #13702]
(From OE-Core rev: 24ca62b3c1fd404b67d549b29aeeacf913e6dc86)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/oeqa/selftest/cases/sysroot.py')
-rw-r--r-- | meta/lib/oeqa/selftest/cases/sysroot.py | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/meta/lib/oeqa/selftest/cases/sysroot.py b/meta/lib/oeqa/selftest/cases/sysroot.py new file mode 100644 index 0000000000..6e34927c90 --- /dev/null +++ b/meta/lib/oeqa/selftest/cases/sysroot.py | |||
@@ -0,0 +1,37 @@ | |||
1 | # | ||
2 | # SPDX-License-Identifier: MIT | ||
3 | # | ||
4 | |||
5 | import uuid | ||
6 | |||
7 | from oeqa.selftest.case import OESelftestTestCase | ||
8 | from oeqa.utils.commands import bitbake | ||
9 | |||
10 | class SysrootTests(OESelftestTestCase): | ||
11 | def test_sysroot_cleanup(self): | ||
12 | """ | ||
13 | Build sysroot test which depends on virtual/sysroot-test for one machine, | ||
14 | switch machine, switch provider of virtual/sysroot-test and check that the | ||
15 | sysroot is correctly cleaned up. The files in the two providers overlap | ||
16 | so can cause errors if the sysroot code doesn't function correctly. | ||
17 | Yes, sysroot-test should be machine specific really to avoid this, however | ||
18 | the sysroot cleanup should also work [YOCTO #13702]. | ||
19 | """ | ||
20 | |||
21 | uuid1 = uuid.uuid4() | ||
22 | uuid2 = uuid.uuid4() | ||
23 | |||
24 | self.write_config(""" | ||
25 | PREFERRED_PROVIDER_virtual/sysroot-test = "sysroot-test-arch1" | ||
26 | MACHINE = "qemux86" | ||
27 | TESTSTRING_pn-sysroot-test-arch1 = "%s" | ||
28 | TESTSTRING_pn-sysroot-test-arch2 = "%s" | ||
29 | """ % (uuid1, uuid2)) | ||
30 | bitbake("sysroot-test") | ||
31 | self.write_config(""" | ||
32 | PREFERRED_PROVIDER_virtual/sysroot-test = "sysroot-test-arch2" | ||
33 | MACHINE = "qemux86copy" | ||
34 | TESTSTRING_pn-sysroot-test-arch1 = "%s" | ||
35 | TESTSTRING_pn-sysroot-test-arch2 = "%s" | ||
36 | """ % (uuid1, uuid2)) | ||
37 | bitbake("sysroot-test") | ||