long-running tests should be examined and shortened
Bug #619946 reported by
Monty Taylor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
Medium
|
Patrick Crews | ||
Dexter |
Fix Released
|
Medium
|
Patrick Crews |
Bug Description
We have several tests in the test suite which take an extra long amount of time. For instance:
mysql_protocol.
main.innodb-
main.innodb [ pass ] 155171
main.innodb_mysql [ pass ] 154243
Hundreds of seconds is just ridiculous. We should figure out what's going on here and make these tests sensible.
Related branches
lp:~patrick-crews/drizzle/bug619946-test-speed-up
- Drizzle Merge Team: Pending requested
-
Diff: 168 lines (+42/-2)8 files modifiedplugin/transaction_log/tests/r/select_for_update.result (+6/-0)
plugin/transaction_log/tests/t/select_for_update.inc (+9/-0)
tests/include/mix1.inc (+5/-0)
tests/r/innodb-semi-consistent.result (+3/-0)
tests/r/innodb.result (+3/-0)
tests/r/innodb_mysql.result (+3/-0)
tests/t/innodb-semi-consistent.test (+7/-2)
tests/t/innodb.test (+6/-0)
To post a comment you must log in.
On Wed, 18 Aug 2010 16:03:17 -0000, Monty Taylor <email address hidden> wrote: prototest [ pass ] 127885
> mysql_protocol.
prototest does a very exhaustive protocol test.... probably can only be
parallelised.
> main.innodb- semi-consistent [ pass ] 102035
> main.innodb [ pass ] 155171
> main.innodb_mysql [ pass ]
> 154243
These tests should both probably be split up. They do *waaay* too much.
--
Stewart Smith