Hi everyone! Since Didier is off for his trip to FOSDEM he asked me to temporarily take over and write todays landing-team e-mail.
So, sadly, we have decided to not promote a new image for today. There have been many many new landings happening and even though the smoketesting test results weren't as bad as we were suspecting, it's still not the quality we are expecting from our promoted images. But we are working on resolving those issues so that we can have a green image next week! As for the image status - the last test results (for #156) show 5 autopilot failures and a few application crashes. I have tried looking into one of the unity8 crashes on install-and-boot tests, but it seems the crash file is corrupt. We had this crash once before from what we know. Some of the test failures were 'expected', but there also were some new ones. The security test resulted in a failure (!) [1] - both me and Timo were looking into this. With the help of Jamie and Ted we are trying to find the exact culprit - we are suspecting a recent upload of upstart-app-lanuch that happened but it's nothing certain. The test failures are hard to reproduce, but we are working on it. We might even ultimately decide to revert the upstart-app-launch upload. As mentioned in yesterday's e-mail, we slowed down with the landings a bit until we could get some test results on the image. There are still many landings queued up - which I will slowly move forward. We will land mostly those changes that are safe. We are also unblocking some pre-requirements for a new mir landing, which I hope will finally happen next week. See you! Cheers, [1] https://bugs.launchpad.net/upstart-app-launch/+bug/1275017 -- Łukasz 'sil2100' Zemczak lukasz.zemc...@canonical.com www.canonical.com -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp