CI failures
Daniel van Vugt
daniel.van.vugt at canonical.com
Wed Dec 18 06:58:59 UTC 2013
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-trusty-touch/78/console
(why can't I see any useful log there?)
- Daniel
On 17/12/13 15:49, Daniel van Vugt wrote:
> 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 issues still blocking CI. If you find them, please
> use tag "blockingci".
>
> - Daniel
>
>
> On 12/12/13 09:40, Daniel van Vugt wrote:
>> 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. 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, 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 tests when they start to fail.
>>>
>>> [1] http://s-jenkins.ubuntu-ci:8080/job/mir-mediumtests-trusty-touch/8/
>>>
>>> On Wed, Dec 11, 2013 at 4:04 AM, Daniel van Vugt
>>> <daniel.van.vugt at canonical.com <mailto:daniel.van.vugt at canonical.com>>
>>> wrote:
>>>
>>> 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-mir-development-__branch-ci/514/
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/514/>
>>>
>>>
>>> Executed test runs:
>>> FAILURE:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-android-trusty-i386-__build/401/console
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-android-trusty-i386-build/401/console>
>>>
>>>
>>> SUCCESS:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-clang-trusty-amd64-__build/397
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-clang-trusty-amd64-build/397>
>>> FAILURE:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-mediumtests-trusty-__touch/6/console
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-mediumtests-trusty-touch/6/console>
>>>
>>> SUCCESS:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-team-mir-development-__branch-trusty-amd64-ci/240
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-amd64-ci/240>
>>>
>>>
>>> deb:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-team-mir-development-__branch-trusty-amd64-ci/240/__artifact/work/output/*zip*/__output.zip
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-amd64-ci/240/artifact/work/output/*zip*/output.zip>
>>>
>>>
>>> SUCCESS:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-team-mir-development-__branch-trusty-armhf-ci/243
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-armhf-ci/243>
>>>
>>>
>>> deb:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-team-mir-development-__branch-trusty-armhf-ci/243/__artifact/work/output/*zip*/__output.zip
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-armhf-ci/243/artifact/work/output/*zip*/output.zip>
>>>
>>>
>>> SUCCESS:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-mediumtests-builder-__trusty-armhf/6
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-trusty-armhf/6>
>>>
>>> deb:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-mediumtests-builder-__trusty-armhf/6/artifact/work/__output/*zip*/output.zip
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-trusty-armhf/6/artifact/work/output/*zip*/output.zip>
>>>
>>>
>>> FAILURE:
>>>
>>> http://jenkins.qa.ubuntu.com/__job/mir-mediumtests-runner-__mako/45/console
>>>
>>>
>>>
>>> <http://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/45/console>
>>>
>>> SUCCESS:
>>> http://s-jenkins.ubuntu-ci:__8080/job/touch-flash-device/__2218
>>> <http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/2218>
>>>
>>> Click here to trigger a rebuild:
>>>
>>> http://s-jenkins.ubuntu-ci:__8080/job/mir-team-mir-__development-branch-ci/514/__rebuild
>>>
>>>
>>>
>>> <http://s-jenkins.ubuntu-ci:8080/job/mir-team-mir-development-branch-ci/514/rebuild>
>>>
>>>
>>>
>>>
>>
>
More information about the Mir-devel
mailing list