Merge lp:~canonical-platform-qa/webbrowser-app/autopkgtest into lp:webbrowser-app
| Status: | Rejected |
|---|---|
| Rejected by: | Olivier Tilloy on 2016-03-15 |
| Proposed branch: | lp:~canonical-platform-qa/webbrowser-app/autopkgtest |
| Merge into: | lp:webbrowser-app |
| Diff against target: |
163 lines (+118/-3) 3 files modified
README (+57/-3) debian/tests/control (+26/-0) debian/tests/touch-session-autopilot (+35/-0) |
| To merge this branch: | bzr merge lp:~canonical-platform-qa/webbrowser-app/autopkgtest |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Olivier Tilloy | Disapprove on 2016-03-15 | ||
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-05-27 | |
| Martin Pitt | 2015-04-20 | Needs Fixing on 2015-05-05 | |
|
Review via email:
|
|||
Commit Message
Added the dep8 tests and instructions on the README to run them in qemu or on the phone.
Description of the Change
This introduces dep8 tests that can be run against a local qemu instance (optionally configured against -proposed) as well as a local phone.
It runs the two autopilot suites one dep8 test by autopilot suite (see README for adt-run runes).
| Leo Arias (elopio) wrote : | # |
| Brendan Donegan (brendan-donegan) wrote : | # |
Small comment about where the docs go
| Olivier Tilloy (osomon) wrote : | # |
Also note that this source package contains two autopilot test suites: webbrowser_app and webapp_container. I guess both should be run.
| Leo Arias (elopio) wrote : | # |
Thanks for the review Brendan. Reply inline. Please let me know what do you think.
| Leo Arias (elopio) wrote : | # |
> Also note that this source package contains two autopilot test suites:
> webbrowser_app and webapp_container. I guess both should be run.
I'm giving that a try...
| Vincent Ladeuil (vila) wrote : | # |
This now passes the tests against the current archive, -proposed and the phone (krillin devel-proposed 196).
@Leo: Feedback welcome, there may still be some rough edges and bits we'd like to be ready for reuse in other projects but I think that can wait.
| Brendan Donegan (brendan-donegan) wrote : | # |
Small suggestion
| Martin Pitt (pitti) wrote : | # |
Nice work! This should get some cleanup (see inline comments), but by and large LGTM.
This is a good prototype for seeing what we need to fix in our infrastructure to eventually not make this an eyebrow-riser, so once we can massage these tests to be simple again we can declare victory :-)
| Martin Pitt (pitti) wrote : | # |
Also, I don't think we want to have all that README spread out/duplicated into all of our packages, but rather centrally in README.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:977
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 978. By Vincent Ladeuil on 2015-04-23
-
From pitti's review: remove wrappers, use Test-Command instead. Import ubuntu-
touch-session env in a non-barbaric way. - 979. By Vincent Ladeuil on 2015-04-23
-
Revert the needs-recommends tweak, it's too greedy and on the phone it trigger importing python3-xlib which in turn triggers a bug in autopilot automatic platform detection.
| Vincent Ladeuil (vila) wrote : | # |
Thanks a lot for the reviews pitti/brendand.
I've made a some modifications and pushed them.
Discussed on IRC:
- ADT_NORMAL_USER is not available for tests so keep using $USER
- ubuntu-
I tried needs-recommends instead of explicitly specifying python3-evdev but it broke on the phone so I reverted that part. My gut feeling is that python3-xlib is installed on the phone and confuses autopilot.
We may want to fix autopilot though.
| Vincent Ladeuil (vila) wrote : | # |
> Also, I don't think we want to have all that README spread out/duplicated into
> all of our packages, but rather centrally in README.
> wiki?
Sorry, I missed that comment earlier.
I'm -0 here, until everybody knows how to use adt-run, I'm not against some doc duplication.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:979
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Vincent Ladeuil (vila) wrote : | # |
> > Also, I don't think we want to have all that README spread out/duplicated
> into
> > all of our packages, but rather centrally in README.
> > wiki?
>
> Sorry, I missed that comment earlier.
>
> I'm -0 here, until everybody knows how to use adt-run, I'm not against some
> doc duplication.
Meh, upon reflection I think we should indeed centralize the doc AND point to it from the README. What's the URL I should use ?
| Federico Gimenez (fgimenez) wrote : | # |
Looks really great! One inline comment about test dependencies.
Don't know if it's relevant at this stage but I'm getting this [1] following the README for qemu and the current archive, there's an error for the first test:
bash: line 8: /tmp/tmp.
Thanks!
| Federico Gimenez (fgimenez) wrote : | # |
Looks really great! One inline comment about test dependencies.
Don't know if it's relevant at this stage but I'm getting this [1] following the README, there's an error for the first test:
bash: line 8: /tmp/tmp.
Thanks!
| Federico Gimenez (fgimenez) wrote : | # |
Looks really great! One inline comment about test dependencies.
Don't know if it's relevant at this stage but I'm getting this [1] following the README for qemu and the current archive, there's an error for the first test:
bash: line 8: /tmp/tmp.
Thanks!
| Federico Gimenez (fgimenez) wrote : | # |
Looks really great! One inline comment about test dependencies.
Don't know if it's relevant at this stage but I'm getting this [1] following the README for qemu and the current archive, there's an error for the first test:
bash: line 8: /tmp/tmp.
Thanks!
| Federico Gimenez (fgimenez) wrote : | # |
Looks really great! One inline comment about test dependencies.
Don't know if it's relevant at this stage but I'm getting this [1] following the README for qemu and the current archive, there's an error in the first test:
bash: line 8: /tmp/tmp.
Thanks!
- 980. By Vincent Ladeuil on 2015-04-24
-
Clarify why autopkgtest is a test dependency.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:980
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Martin Pitt (pitti) wrote : | # |
Thanks Vincent for the updates! One important bug (sudo -A) left, the others are nitpicks.
- 981. By Vincent Ladeuil on 2015-05-05
-
Mention the prefered targets for the documentation about running dep8 tests.
- 982. By Vincent Ladeuil on 2015-05-05
-
XS-Testsuite isn't necessary at all any more, dpkg-source adds this automatically now. (from pitti's review).
- 983. By Vincent Ladeuil on 2015-05-05
-
Remove the FIXME, explicitly Depend'ing on python3-evdev is fine. Added 'Classes: ubuntu-touch' to document the target test class (currently a no-op).
- 984. By Vincent Ladeuil on 2015-05-05
-
Use -A for sudo or the test can hang if sudo asks for a password.
| Vincent Ladeuil (vila) wrote : | # |
Thanks for the review !
All fixed as mentioned in the inline comments.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:984
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:984
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:984
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Olivier Tilloy (osomon) wrote : | # |
Any update on:
+.. FIXME: This shouldn't be part of a specific package but instead be part
+ of the wiki
+ https:/
+ of autopkgtest README.
?
| Olivier Tilloy (osomon) wrote : | # |
As far as the changes themselves, they look ok to me (I’m not really familiar with autopkgtests so I’ll trust Martin’s thorough review). I’ve tested the instructions and got errors while running the actual tests, but the runners seemed to be doing their job.
| Leo Arias (elopio) wrote : | # |
Thanks for looking at this Olivier.
But it's really important that all the tests are passing, otherwise you won't be able to land an update to the archive.
We need to either fix them or select a subset of tests to begin with. Can you please paste the errors you are getting?
- 985. By Vincent Ladeuil on 2015-05-18
-
Remove the FIXME about doc by refering to the official autopkgtest documentation and dropping the proposed-migration example as it's not defined by the project.
| Vincent Ladeuil (vila) wrote : | # |
> Any update on:
>
> +.. FIXME: This shouldn't be part of a specific package but instead be part
Sorry about the delay, I somehow never seen that comment :-/
Fixed now.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:985
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Vincent Ladeuil (vila) wrote : | # |
> Thanks for looking at this Olivier.
> But it's really important that all the tests are passing, otherwise you won't
> be able to land an update to the archive.
A bit of clarification here, proposed-migration will not block for tests that always failed in the past.
Since this is the first dep8 test, the landing won't be blocked.
Once the test is passing though, yes, new failures will block the landing.
>
> We need to either fix them or select a subset of tests to begin with. Can you
> please paste the errors you are getting?
From http://
The following packages have unmet dependencies:
webbrowser-app : Depends: liboxideqt-
E: Unable to correct problems, you have held broken packages.
ADB_RC=100
So,
1) it's failing on mako (which won't happen in proposed-migration (we're still far from running tests on phones in the proposed-migration)
2) I can use some help understanding the failure there as I don't quite get where liboxideqt-
| Olivier Tilloy (osomon) wrote : | # |
> I can use some help understanding the failure there as I don't quite
> get where liboxideqt-
The release pocket of vivid has oxide 1.5.5-0ubuntu1.
The updates and security pockets have oxide 1.6.6-0ubuntu0.
The vivid overlay PPA has oxide 1.7.7-0ubuntu0.
| Vincent Ladeuil (vila) wrote : | # |
> > I can use some help understanding the failure there as I don't quite
> > get where liboxideqt-
>
> The release pocket of vivid has oxide 1.5.5-0ubuntu1.
> The updates and security pockets have oxide 1.6.6-0ubuntu0.
> The vivid overlay PPA has oxide 1.7.7-0ubuntu0.
am I looking at the wrong place ?
| Vincent Ladeuil (vila) wrote : | # |
> It's not in https:/
> /stable-
>
> am I looking at the wrong place ?
Yes and no ;) It's part of oxide-qt so available there, the -ci job mentions adding the overlay ppa too.
But apt-get doesn't find it...
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:985
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Vincent Ladeuil (vila) wrote : | # |
Ok, so, the issue is that -ci use ubuntu/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:985
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Vincent Ladeuil (vila) wrote : | # |
.... and:
$ rmadison liboxideqt-
...
liboxideqt-
@Olivier: Do you know why 1.7 is only in wily-proposed ? What's the way out of this situation ?
| Olivier Tilloy (osomon) wrote : | # |
@vila: migration of oxide 1.7.7 from proposed to release was blocked on some autopkgtest failure, it has now been resolved.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:985
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:985
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Olivier Tilloy (osomon) wrote : | # |

Not yet ready for review because if we land this and the tests are run when the package is being upgraded in the archive, they will fail because the infrastructure is not ready yet to pass the --setup-command.