=Introduction= there has been a number of bugs filed against failing systemd services, or units, that appear to be random and very hard to reproduce. The bugs have been found at the autobuilder instances and not much information about what caused the failure can be found
example bugs for the aforementioned errors are YOCTO#8142 and YOCTO#8141, there are others these errors seemingly can be reproduced by constraining the resources on the target for testing, putting a low amount of CPU at disposal and making it test with other test targets simultaneously to also constrain IO has gotten the failure to show up often enough to debug it further debug showed that the service tests were failing due to the kernel booting in a long time, a number of seconds that exceeds systemd's timeout for units to finalize coming up. 404 failure samples were checked and all of them showed a boot time that exceeded the timeout =Change Description= this change creates a test that measures the target boot time against the unit timeout default, which is 90 seconds. If the booting time exceeded 90 seconds then the test fails the tests that check for systemd services are now dependant upon this test, if the boot time test fails then the tests that check services will be skipped Benjamin Esquivel (2): systemd: test target boot time against unit timeout systemd: skip service tests on long boot times meta/lib/oeqa/runtime/systemd.py | 83 +++++++++++++++++++++++++++++++++++++--- 1 file changed, 78 insertions(+), 5 deletions(-) -- 1.8.4.5 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core