linux/poky.git/scripts, branch yocto-4.0.31

scripts/install-buildtools: Update to 4.0.30

2025-10-14T14:20:36+00:00

Update to the 4.0.30 release of the 4.0 series for buildtools (From OE-Core rev: 237452d023dfc895cd8183e30e781da6f60b2ec5) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 4.0.28

2025-07-30T14:47:48+00:00

Update to the 4.0.28 release of the 4.0 series for buildtools (From OE-Core rev: 8e59118164d6468443db211d9ade058402f21add) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 4.0.27

2025-06-20T15:06:30+00:00

Update to the 4.0.27 release of the 4.0.27 series for buildtools (From OE-Core rev: 9277fae3c81a269994faa6ba6f6c9bdfc74e11bd) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 4.0.26

2025-05-16T15:58:06+00:00

Update to the 4.0.26 release of the 4.0 series for buildtools (From OE-Core rev: 04ff268291598c1e0588cff43df694a714e48746) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scritps/runqemu: Ensure we only have two serial ports

2025-02-24T15:00:53+00:00

I have a theory that some of the console boot issues we're seeing are due to starting images with three serial ports yet only starting gettys on two of them. This means that occasionally, depending on the port numbering we may not get a login prompt on the console we expect it on. To fix this, change the runqemu code so that if serial ports are passed in on the commandline (as is the case in automated testing), we don't add any other GUI serial consoles. We do need to make sure we do have at least two serial ports since we don't want getty timeout warnings. (From OE-Core rev: 44e1279970d306b0da4fcc11f9e780915f481819) Signed-off-by: Richard Purdie (cherry picked from commit 1b0348535dce3b776efbcf26406b94730a51eb85) Signed-off-by: Ming Liu Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 4.0.24

2025-02-24T15:00:53+00:00

Update to the 4.0.24 release of the 4.0 series for buildtools. (From OE-Core rev: 93b1e2cbee96bd8731a5d5d0fe5462c2518fe8a7) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

scripts/install-buildtools: Update to 4.0.23

2025-01-24T15:49:28+00:00

Update to the 4.0.23 release of the 4.0 series for buildtools. (From OE-Core rev: 2effc054b1484dd3c87652267bf590c17d2d6f76) Signed-off-by: Aleksandar Nikolic Signed-off-by: Steve Sakoman

resulttool: Improve repo layout for oeselftest results

2024-12-09T15:54:03+00:00

Having all oe-selftest results on top of each other results in a large 640MB json file which is hard to use. Split the results out per machine and test type. This also stops the toolchain raw logs from overwriting each other meaning more than one MACHINE is preserved. (From OE-Core rev: e42b6a40a3a01e328966bb5ee1bb3e0993975b15) Signed-off-by: Richard Purdie (cherry picked from commit 4b890f04bc7d147b4a11b824a84f3d2abd75ac54) Signed-off-by: Steve Sakoman

resulttool: Trim the precision of duration information

2024-12-09T15:54:03+00:00

The duration values have pointless amounts of precision. Removing some of the least significant digits reduces result size and makes the results easier to read. (From OE-Core rev: 4ec9bb7e1a02de8223fb7485fc47cb43ad19093c) Signed-off-by: Richard Purdie (cherry picked from commit a789a2e6d97bb8efd663226a17db8d1ca6c1e40f) Signed-off-by: Steve Sakoman

resulttool: Clean up repoducible build logs

2024-12-09T15:54:03+00:00

We've improved the data stored for reproduicible builds. Teach resulttool how to apply those cleanups when reprocessing data so we can reduce results file sizes and make the data easier to process. (From OE-Core rev: cf1b4eb85ca3cb62c9746c6dc8f6dc9c4802c142) Signed-off-by: Richard Purdie (cherry picked from commit b799c57ae6d61c1b1c7035c8a2c4ba6ee08d1a81) Signed-off-by: Steve Sakoman