canonical-ci-engineering team mailing list archive

[Francis Ginther <francis.ginther@xxxxxxxxxxxxx>]

Martin,

The piece you are most likely missing is the script inside the jenkins
job itself, [4].

Now the proper solution is that we should not have any logic in the
jenkins jobs itself. It should all be included in the test runner
branch or we should be using a standard test runner approach. Both
would allow us to write simpler documentation to enable developers to
run this at home. These are things that we need to clean-up this
cycle. These test runners are not private, so there is no reason not
do document them on the public wiki.

[4] - http://paste.ubuntu.com/6324303/

Francis

On Tue, Oct 29, 2013 at 7:02 AM, Martin Pitt <martin.pitt@xxxxxxxxxx> wrote:
> Hey Francis,
>
> mailing you directly as I'm almost certainly not allowed to mail
> canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx.
>
> There is an obstinate failure of the messaging-app tests [1] in the
> otto runner. The app starts, the widgets appear, it can type a number
> into the receiver line, but the actual text message line stays
> inactive. Both the autopilot test failure exception and the video
> agree on this.
>
> But I can't for the life of it reproduce that in a saucy or
> (dist-upgraded) trusty live CD environment in KVM, and last week not
> even in a manually started otto container with running the tests
> manually.
>
> So I need to be able to exactly reproduce the otto runner locally.
> Siva pointed out [2]
> which I checked out, but it's not quite clear how to use it. I don't
> know what "overrides" are, and the only two command line switches it
> has talk about those.
>
> So what I have is:
>
>  * the autopilot-testrunner-otto-saucy checkout
>  * an otto checkout with a workaround for the swap kernel config so
>    that it actually works in saucy/trusty
>  * a saucy final ISO (we don't have trusty ones yet)
>  * the output.zip from the CI builds from my branch with the test
>    cases [3]
>
> How do I plug these together to run the tests from
> messaging-app-autopilot (as shipped in [3]) on my workstation?
>
> I envision this is a rather common scenarario, but I didn't find
> anything about that in e. g.
> https://wiki.canonical.com/UbuntuEngineering/CI/Playbook/UpstreamMerger
> or the parent pages. I'm happy to add that to wiki.ubuntu.com once I
> understand how it works, as that's the kind of documentation which
> really ought to be public. It seems there is no /CI hierarchy there,
> but at some point there ought to be so I could just as well create the
> first page there :)
>
> Thanks,
>
> Martin
>
> [1] https://code.launchpad.net/~pitti/messaging-app/phonesim-tests/+merge/191121
> [2] lp:~canonical-ci-engineering/jenkins-launchpad-plugin/autopilot-testrunner-otto-saucy
> [3] e. g.  http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-trusty-amd64/150/artifact/work/output/*zip*/output.zip
> --
> Martin Pitt                        | http://www.piware.de
> Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)



-- 
Francis Ginther
Canonical - Ubuntu Engineering - Continuous Integration Team