For Image 181, Mako ran great on the first try. All tests passed, with
just the two known .crash artifacts.
On Maguro, it got 99 tests into it and had a device problem during the
unity8 run. I've restarted on another device and got past that point
now though, and we'll get someone local to look i
On Thu, Feb 13, 2014 at 2:19 PM, Paul Larson wrote:
> == Maguro ==
> [...]
> * unity8 -
> [...]
> - test_open_applications_scope(Native Device)
>
[...]
Hey, I think I've found a video that shows what's going wrong here:
https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/2846/art
Hello, I'm Natan, Brazillian guy.
I'm new here, and need a help, rs'
I have some doubts
2014-02-13 20:24 GMT-02:00 Robert Park :
> On Thu, Feb 13, 2014 at 9:43 AM, Didier Roche wrote:
> > This one is built and executing tests as we speak. As soon as the tests
> > results are telling we don't
On Thu, Feb 13, 2014 at 9:43 AM, Didier Roche wrote:
> This one is built and executing tests as we speak. As soon as the tests
> results are telling we don't have regressions, a new image (181) with latest
> Mir will be kicked in.
Ok, image 181 is now built with the new Mir and
unity-scope-medias
Image 180 results:
== Mako ==
First run, we had a crash with unity8 which still showed up after
rerunning. Also, camera_app didn't work because the screen unlocker
had some problem before the run, but this was fine after rerunning it.
== Maguro ==
* default - dns failure on apt-get install test. P
On 02/13/2014 12:43 PM, Didier Roche wrote:
On the testing front, we have one new regression on the toolkit. Timo
talked with upstream and it seems that the next ubuntu-ui-toolkit has
a fix to make that flaky behavior better. The other failures are flaky
tests on mako and maguro and Nicholas wi
6 matches
Mail list logo
