Merge lp://staging/~matsubara/ubuntu-test-cases/lamp-bug-1443987 into lp://staging/ubuntu-test-cases/server
Status: | Merged |
---|---|
Merged at revision: | 100 |
Proposed branch: | lp://staging/~matsubara/ubuntu-test-cases/lamp-bug-1443987 |
Merge into: | lp://staging/ubuntu-test-cases/server |
Diff against target: |
71 lines (+38/-3) 2 files modified
testsuites/lamp/test_mysql_show_tables/tc_control (+4/-2) testsuites/lamp/test_mysql_show_tables/test.py (+34/-1) |
To merge this branch: | bzr merge lp://staging/~matsubara/ubuntu-test-cases/lamp-bug-1443987 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robie Basak | Approve | ||
Paul Larson (community) | Approve | ||
Review via email: mp+256347@code.staging.launchpad.net |
This proposal supersedes a proposal from 2015-04-15.
Commit message
Update lamp test case that checks the number of default mysql tables installed
Description of the change
Hi, this branch fixes the failing vivid smoke test for LAMP[1] by updating the number of default MySQL tables the test looks for. I have a question though, if I update this branch, will older releases such as trusty rely on this new test case? If yes, those are going to fail as well since on trusty the default mysql version installs only 24 tables, IIRC.
Should I special case the test case or does trusty use another branch for its test runs?
[1] http://
Would this break things in the trusty jobs though? It looks like there have been no daily images for trusty in a while, but I'm guessing there will be at some point right?