Merge lp:~mterry/libunity/enable-tests into lp:libunity
| Status: | Merged |
|---|---|
| Approved by: | Michael Terry on 2012-11-16 |
| Approved revision: | 197 |
| Merged at revision: | 197 |
| Proposed branch: | lp:~mterry/libunity/enable-tests |
| Merge into: | lp:libunity |
| Diff against target: |
34 lines (+3/-3) 3 files modified
debian/changelog (+2/-1) debian/control (+1/-0) debian/rules (+0/-2) |
| To merge this branch: | bzr merge lp:~mterry/libunity/enable-tests |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2012-11-16 | |
| Didier Roche | Approve on 2012-11-08 | ||
| Stephen M. Webb (community) | 2012-11-07 | Approve on 2012-11-07 | |
|
Review via email:
|
|||
Commit Message
Enable tests during debian build
Description of the Change
Enable tests for libunity at debian build time.
| Didier Roche (didrocks) wrote : | # |
I'm getting this issue in my pbuilder:
/bin/bash: line 9: ./bug-1062331.py: Permission denied
FAIL: bug-1062331.py
/bin/bash: line 9: ./extras.py: Permission denied
FAIL: extras.py
===================
2 of 2 tests failed
===================
make[4]: *** [check-TESTS] Error 1
Can you give it a look? Do you have the same issue on your machine?
| Michael Terry (mterry) wrote : | # |
Didier, I don't see that when building in my pbuilder. Those files are both executable for me too. Do you see them as non-executable somehow?
| Didier Roche (didrocks) wrote : | # |
figure out on IRC, needed a new version to not end up in diff.gz and having the executable bit stripped.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
| Francis Ginther (fginther) wrote : | # |
Jenkins failed due to job configuration error, re-approving after fixing the job.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
| Francis Ginther (fginther) wrote : | # |
Jenkins scripts were not handling a version number bump correctly. Applying a workaround and re-approving.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
| Francis Ginther (fginther) wrote : | # |
grumble... pushed fix to the wrong location. trying again.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
| Michael Terry (mterry) wrote : | # |
Tried to reproduce test failure in an amd64 VM, but couldn't. So I'll try to approve again on the chance it was a fluke.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
| Martin Mrazik (mrazik) wrote : | # |
I was seeing the same (random) fail/pass in bamf :-/ There seems to be something broken in the auto test.
See the last comment -- it passed on i386 but failed for amd64.
| Michael Terry (mterry) wrote : | # |
Saw another libunity branch land, so trying again.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
- 197. By Michael Terry on 2012-11-16
-
merge from trunk

+1