CI failures

2014-09-23 Thread Kevin DuBois
So it seems there's a problem with the CI where the images have selected the mesa egl configuration: https://bugs.launchpad.net/mir/+bug/1372926 This should be fixed in the next image release, but for the time being, we're stuck with the CI failures. Cheers, Kevin -- Mir-devel mailin

Re: CI failures

2013-12-17 Thread Daniel van Vugt
Chris, We still have some weird CI failures that are not the fault of Mir: https://jenkins.qa.ubuntu.com/job/mir-android-trusty-i386-build/472/consoleFull https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/112/console and perhaps: https://jenkins.qa.ubuntu.com/job/mir-mediumtests

Re: CI failures

2013-12-16 Thread Daniel van Vugt
Actually, they're not fixed. Which is why very little has landed this past week... https://bugs.launchpad.net/mir/+bugs?field.tag=blockingci One is a minor scripting issue due to changes in libhybris. The other is an annoyingly intermittent (Galaxy)Nexus(/4) test failure. There may be other

Re: CI failures

2013-12-11 Thread Daniel van Vugt
Of course I was not suggesting disabling tests. Just to disable broken test _machines_. It appears they're all fixed today, so problem solved :) On 12/12/13 00:01, Chris Gagnon wrote: The demos say there is an error because of output on stderr, but it won't fail the build because of it. Curre

Re: CI failures

2013-12-11 Thread Alan Griffiths
On 11/12/13 16:01, Chris Gagnon wrote: > These tests pass when I ran CI on the current trunk of the > mir-development branch[1] and the tests passed, the test also passed > before enabling CI more than one time. It looks like the new code is > causing these tests to fail. > > We cannot disable t

Re: CI failures

2013-12-11 Thread Chris Gagnon
The demos say there is an error because of output on stderr, but it won't fail the build because of it. Currently it will block the build when an integration test or acceptance test fails. These tests pass when I ran CI on the current trunk of the mir-development branch[1] and the tests passed,

CI failures

2013-12-11 Thread Daniel van Vugt
It seems CI has become a little over-ambitious recently and no branch can pass all the runs. Can we disable the broken ones? On 11/12/13 17:01, PS Jenkins bot wrote: Review: Needs Fixing continuous-integration FAILED: Continuous integration, rev:1282 http://jenkins.qa.ubuntu.com/job/mir-team-