linux/poky.git/meta-selftest/recipes-test, branch styhead-5.1.4Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=styhead-5.1.42024-09-01T10:05:20+00:00oeqa/selftest/bbclasses: Add tests for systemd and update-rc.d interaction2024-09-01T10:05:20+00:00Peter Kjellerstedtpkj@axis.com2024-08-20T19:54:40+00:00urn:sha1:b971a3a77cfc01de9dc83e97afc990081f4b9166
These tests verify that the correct files are left behind when systemd
is inherited and depending on whether the systemd and/or sysvinit distro
features are enabled.
(From OE-Core rev: 4ef25caa00ad08046567d0e7f4523486c3a256d0)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
selftest-hardlink: Add additional test cases2024-07-22T15:53:06+00:00Mark Hatlemark.hatle@amd.com2024-07-19T18:58:18+00:00urn:sha1:4462724cab96ed3990fdf9b30edcea2adc9095ee
Additional test cases for debug symlink generation both binaries
and static libraries.
This also has the side effect of testing for race conditions in the
hardlink debug generation and stripping.
(From OE-Core rev: 7171f41c07a39a7543bb64f075d38b8e74563089)
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
selftest/fortran-helloworld: Fix buildpaths error2024-07-15T12:12:51+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-07-15T12:10:46+00:00urn:sha1:480dc1c0dfeb053b880ea733e72b4c639e9a9d8a
There is a buildpaths QA error in the test recipe that somehow didn't show up
in earlier testing. Use a source directory and tweak the build command to
avoid embedding build paths in the generated binary.
(From OE-Core rev: 8f1cfaf2be834217cd1cf5be98f44270c36cc31a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
selftest: add Upstream-Status to .patch files2024-06-10T13:27:24+00:00Martin Jansamartin.jansa@gmail.com2024-06-05T18:29:24+00:00urn:sha1:582b2627a80f20e641e39141962a2ea972f729f0
(From OE-Core rev: e5e5561c178a565b3aa7cb540fe1c8f71917c882)
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
recipes: Ensure S is set to a valid directory2024-05-21T11:08:04+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-15T06:53:23+00:00urn:sha1:a5cea4c0b49792408edfe5f68e92900acb860cef
Several recipes have S pointing at a directory that does not exist.
Set S in these cases to somethig valid making the metadata and
recipe behaviour more consistent.
Tweak one of the QA test diff offsets to match the changed recipe.
(From OE-Core rev: 22f1f5849a9a3bf287dbe8933546e52e39ddc86e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
devtool: Drop oe-local-files and simplify2024-05-21T11:08:04+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-01T21:36:50+00:00urn:sha1:6d77296d83f87ea7f6ca0363a947d3eac721459b
The only real reason for oe-local-files was to support S = WORKDIR. With changes to
drop support for that, it makes sense to simplify devtool and to try and make both
the code and the processes/workflows simpler.
This patch drops support for S = WORKDIR, removes oe-local-files and then updates
the test cases to match this new situation.
At the code level, we assume we can always now track code changes using git and
that things committed into git are handled as patches (as before) but delta against
HEAD is saved as specific file level changes to the recipe.
One test is disabled as it is no longer approproate. It is being keped until we can
make WORKDIR != UNPACKDIR at which point it should be revisited.
(From OE-Core rev: ce8190c519052fed10b5233697b69a75868db45a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
recipes: Switch away from S = WORKDIR2024-05-21T11:08:04+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-01T21:52:57+00:00urn:sha1:d6ae8d2004f8ac3aab4571e0077d406b2d19b542
Where recipes use S = ${WORKDIR}, change them to set UNPACKDIR to
a subdir of WORKDIR and make S point at this instead.
I've chosen not to force S into any standard UNPACKDIR we may pick in
future just so the S = UNPACKDIR case is clearly visible by the
directory naming under WORKDIR as that should aid usability.
(From OE-Core rev: d9328e3b0b062f0621de3d114584b44f384a1c02)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
recipes: Start WORKDIR -> UNPACKDIR transition2024-05-21T11:08:04+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-09T16:02:39+00:00urn:sha1:71c6db8e65ced98db74fd18b726fa4b4c0346f05
Replace references of WORKDIR with UNPACKDIR where it makes sense to do
so in preparation for changing the default value of UNPACKDIR.
(From OE-Core rev: 1f18b9a512800860d5153d89eb82b56388efad6f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
recipes: Update WORKDIR references to UNPACKDIR2024-05-02T14:15:51+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-04-30T13:23:37+00:00urn:sha1:0ea63b6a439fe97f840c69d08cf381687baaae3f
Since we want to be able to stop unpacking to WORKDIR, correct the WORKDIR
references in recipe do_compile/do_install tasks to use UNPACKDIR in the
appropraite places instead.
(From OE-Core rev: d73595df69667fe9d12ecd407b77a0b8dae2109c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
recipes: Update S = WORKDIR recipes to use ${S} correctly2024-05-02T14:15:51+00:00Richard Purdierichard.purdie@linuxfoundation.org2024-05-01T21:50:08+00:00urn:sha1:3288587aeb009fb65652776242c0a526b90771e2
Where recipes use S = ${WORKDIR}, ensure they are referencing ${S} correctly
to access files as soon we want to stop doing this in WORKDIR at which point
they would break unless corrected.
(From OE-Core rev: f25dd633fffe6560f191526d1869e657e129bad9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>