Mir

Merge lp://qastaging/~chris.gagnon/mir/enabled-arm-tests into lp://qastaging/mir

  1. enabled-arm-tests
  2. Merge into development-branch
Proposed by Chris Gagnon
Status: Rejected
Rejected by: Chris Gagnon
Proposed branch: lp://qastaging/~chris.gagnon/mir/enabled-arm-tests
Merge into: lp://qastaging/mir
Diff against target: 28 lines (+2/-5)
2 files modified
cmake/MirCommon.cmake (+1/-1)
debian/rules (+1/-4)
To merge this branch: bzr merge lp://qastaging/~chris.gagnon/mir/enabled-arm-tests
Reviewer Review Type Date Requested Status
Daniel van Vugt Needs Fixing
PS Jenkins bot (community) continuous-integration Needs Fixing
Robert Carr (community) Needs Information
Alan Griffiths Pending
Review via email: mp+191991@code.qastaging.launchpad.net

This proposal supersedes a proposal from 2013-10-18.

Description of the change

test MP for jenkins, resubmitting this merge because armhf should be enabled in jenkins now

To post a comment you must log in.
Revision history for this message
Chris Gagnon (chris.gagnon) wrote : Posted in a previous version of this proposal

Ignore this MP, I am using it for testing jenkins

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal

PASSED: Continuous integration, rev:1149
http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/201/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-saucy-i386-build/2427
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-saucy-amd64-build/2312
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/198
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/198/artifact/work/output/*zip*/output.zip

Click here to trigger a rebuild:
http://10.97.0.26:8080/job/mir-team-mir-development-branch-ci/201/rebuild

review: Approve (continuous-integration)
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Posted in a previous version of this proposal

I can't see any logs of Android running tests yet, but expect some to still fail:
https://bugs.launchpad.net/mir/+bugs?field.tag=testsfail

Also linked bug 1203004.

Revision history for this message
Daniel van Vugt (vanvugt) : Posted in a previous version of this proposal
review: Approve
Revision history for this message
Alan Griffiths (alan-griffiths) wrote : Posted in a previous version of this proposal

Hmm, obviously not this MP - but we don't seem to have a armhf CI build anymore. what happened to mir-saucy-armhf-ci?

review: Needs Information
Revision history for this message
Alan Griffiths (alan-griffiths) wrote : Posted in a previous version of this proposal

> Hmm, obviously not this MP - but we don't seem to have a armhf CI build
> anymore. what happened to mir-saucy-armhf-ci?

Ah! We only build armhf when targeting lp:mir...

review: Approve
Revision history for this message
Chris Gagnon (chris.gagnon) wrote : Posted in a previous version of this proposal

I'll update the stack config to build armhf against the dev branch

Revision history for this message
Chris Gagnon (chris.gagnon) wrote : Posted in a previous version of this proposal

https://code.launchpad.net/~chris.gagnon/cupstream2distro-config/mir-dev-enable-armhf/+merge/191987

Revision history for this message
Chris Gagnon (chris.gagnon) wrote :

I resubmitted this merge proposal so jenkins would rebuild it

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

FAILED: Continuous integration, rev:1149
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https://code.launchpad.net/~chris.gagnon/mir/enabled-arm-tests/+merge/191991/+edit-commit-message

http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/211/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-saucy-i386-build/2439
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-saucy-amd64-build/2324
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/208
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/208/artifact/work/output/*zip*/output.zip
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-armhf-ci/1/console

Click here to trigger a rebuild:
http://10.97.0.26:8080/job/mir-team-mir-development-branch-ci/211/rebuild

review: Needs Fixing (continuous-integration)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal

FAILED: Continuous integration, rev:1149
http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/213/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-saucy-i386-build/2441
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-saucy-amd64-build/2326
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/210
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/210/artifact/work/output/*zip*/output.zip
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-armhf-ci/3/console

Click here to trigger a rebuild:
http://10.97.0.26:8080/job/mir-team-mir-development-branch-ci/213/rebuild

review: Needs Fixing (continuous-integration)
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

valgrind seems to be different on arm. Vis:

valgrind: Bad option: --error-exitcode=1 --trace-children=yes
valgrind: Use --help for more information or consult the user manual.

(Not sure why this should be - but running the tests without valgrind would be a step forwards.)

lp://qastaging/~chris.gagnon/mir/enabled-arm-tests updated
1150. By Chris Gagnon

don't do anything special for ANDROID_BUILD in cmake common

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal

FAILED: Continuous integration, rev:1150
http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/232/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-saucy-i386-build/2465
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-saucy-amd64-build/2350
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/229
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/229/artifact/work/output/*zip*/output.zip
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-armhf-ci/22/console

Click here to trigger a rebuild:
http://10.97.0.26:8080/job/mir-team-mir-development-branch-ci/232/rebuild

review: Needs Fixing (continuous-integration)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

FAILED: Continuous integration, rev:1150
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https://code.launchpad.net/~chris.gagnon/mir/enabled-arm-tests/+merge/191991/+edit-commit-message

http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/233/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-saucy-i386-build/2466
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-saucy-amd64-build/2351
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/230
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-amd64-ci/230/artifact/work/output/*zip*/output.zip
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-saucy-armhf-ci/23/console

Click here to trigger a rebuild:
http://10.97.0.26:8080/job/mir-team-mir-development-branch-ci/233/rebuild

review: Needs Fixing (continuous-integration)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

There seem to be plenty of failures:

The following tests FAILED:
   4 - acceptance-tests (Failed)
   5 - unit-tests (Failed)
   6 - integration-tests (Failed)
and provide no detailed log of what failed.

However we knew that would happen. I think we need to work on the known causes:
    https://bugs.launchpad.net/mir/+bugs?field.tag=testsfail
before this proposal can ever land.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, I need to give this an official review so it shows up correctly in my dashboard :)

I think Resubmit... at a later date when the Android test failures are resolved. Because it's not really sensible to land this now and then have CI failing all the time.

review: Needs Resubmitting
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :

Valgrind is failing because it's being run in a chroot and doesn't have access to proc

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

And if you run it on a real Android, you'll still get failures. A couple of these:
  https://bugs.launchpad.net/mir/+bugs?field.tag=testsfail
which need to be resolved first. Not all of them; probably just one or two more fixes are needed for Android.

Revision history for this message
Robert Carr (robertcarr) wrote :

In light of the discussion: https://code.launchpad.net/~chris.gagnon/mir/development-branch-disable-trace-children-android/+merge/192391

What about enabling android CI without valgrind at first. It's certainly better than what we have running now ;)

review: Needs Information
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

As of just today, I think Android CI might actually be able to pass the automated tests. Can you please resubmit or ping Jenkins?

review: Needs Resubmitting
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

FAILED: Continuous integration, rev:1150
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https://code.launchpad.net/~chris.gagnon/mir/enabled-arm-tests/+merge/191991/+edit-commit-message

http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/307/
Executed test runs:
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-android-trusty-i386-build/78/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-trusty-amd64-build/76
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-amd64-ci/36
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-amd64-ci/36/artifact/work/output/*zip*/output.zip
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-trusty-armhf-ci/36/console

Click here to trigger a rebuild:
http://10.97.0.26:8080/job/mir-team-mir-development-branch-ci/307/rebuild

review: Needs Fixing (continuous-integration)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The real fix for bug 1247718 is landing soon. So when it does, this might start passing :)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Is this branch still required? I think we landed an alternative recently... ?

If so then needs fixing:
Text conflict in debian/rules
1 conflicts encountered.

review: Needs Fixing
Revision history for this message
Chris Gagnon (chris.gagnon) wrote :

a different branch was landed marking as rejected

Unmerged revisions

1150. By Chris Gagnon

don't do anything special for ANDROID_BUILD in cmake common

1149. By Chris Gagnon

update debian rules

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches