It seems the patchtest execution in guest is corrupting the content of openembedded-core's .git/config, thus making further executions impossible due to dependencies on such repo. If ran for a first time, guest will do its job and test all mboxes, but when executed for the second time, the machine will stop and halt with the following message: fatal: Not a git repository (or any parent up to mount point /patchtest) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal
Moving to M1
Daniela, can you run the 'create-guest' script and follow directions to launch the new guest machine? The script has not being tested (neither the final indications) so please test it and let me know the result. Use the development branch [1] on the patchtest repo. This script will make it much easier to create the guest machine, so following it, 'identical' machines are produced no matter the host being used. [1] http://git.yoctoproject.org/cgit/cgit.cgi/patchtest/log/?h=create-guest
(In reply to comment #2) > Daniela, > > can you run the 'create-guest' script and follow directions to launch the > new guest machine? The script has not being tested (neither the final > indications) so please test it and let me know the result. The script builds and launches the guest machine as expected. I just had to change poky's branch a few commits before master as it had issues in build-time. > Use the development branch [1] on the patchtest repo. This script will make it much easier to create the guest machine, so following it, 'identical' machines > are produced no matter the host being used. Guest seems to be working fine and the patchtest execution doesn't corrupt openembedded-core's .git/config anymore, but the the machine still halts before testing all mboxes [YOCTO 10765]. I haven't found a pattern here, but out of 61 mboxes, around 45 are tested correctly. > [1] http://git.yoctoproject.org/cgit/cgit.cgi/patchtest/log/?h=create-guest
With the reference script to create the guest machine, the guest machine does not cause the reported problem. Resolving it as not-a-bug.