Hi Alex, Paul
I'm writing scripts that start toaster then launch builds in the same script.
Recent clones of bitbake cause problems with the toaster commands wrapped with
bitbake build commands in a script. The events from the server are being sent
to the observer before it has set up the queue, and the BuildStarted message
specifically is lost.
For the sequence
bitbake --server-only ...
nohup bitbake --observe-only ... &
bitbake <some target>
ToasterUI incorrectly sees TaskStarted events that don't have info from the
lost BuildStarted, the ToasterUI then throws asserts, and no data is written to
the database.
I have written a patch to bitbake logs a message after the first waitEvent
timeout, that a script can then sync on to know ToasterUI is ready.
Our script (not the poky scripts) then looks like the following:
bitbake --server-only ...
nohup bitbake --observe-only ... &
# sync logic goes here spinning on log file message (for some
reasonable limit)
bitbake <some target>
Do you want me to submit this change to toasterui.py to poky-contrib?
Comments?
Thanks,
Dave Lerner
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
