The toaster-container hasn't passed CI for many months, which also means no new images have been deployed. The CI is effectively being ignored, which means that the webhook that runs the CI for each push to the master branch of poky is currently generating noise. Disable the webhook that is poked with each commit to poky, until the toaster-container CI is deemed useful again.
I assume that the refers to Travis, if not then let me know what it does refer to. If someone could help explain why Travis fails but Toaster works, then I will be happy to fix it. I do not know enough about Travis to understand the error logs. They seem to imply that Toaster server does not start up, but I know that Toaster is working in all my direct testing.
David, if that's the case then it sounds like for some reason the tests stagnated vs what is expected. If the toaster-container isn't useful anymore and no one uses it, then there isn't really any reason to spend time trying to fix the tests. However, if it is still useful, I can try to work in some time to help.
Hi Randy, I used to depend on this to catch bitbake changes that broke Toaster, up until it fell over. I would very much like to have this working again. If you could figure it out and also teach me how to maintain it going forward, that would be fabulous. Thanks, David
David, I locally got toaster working for morty, so I suspect the same issue would be for the other items Since this is valuable for you, I'm going to close this bug. I'll probably open another in the future for actually fixing all the issues. I just don't have time to do it right now, and I'm not sure when I'll be able. Of course feel free to log a bug yourself. Then we can discuss how best to make sure that this remains useful for you.
The toaster-container is working with Travis again.