long-running tests should be examined and shortened

Bug #619946 reported by Monty Taylor
6
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.prototest [ pass ] 127885
main.innodb-semi-consistent [ pass ] 102035
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

Revision history for this message
Stewart Smith (stewart) wrote : Re: [Bug 619946] [NEW] long-running tests should be examined and shortened

On Wed, 18 Aug 2010 16:03:17 -0000, Monty Taylor <email address hidden> wrote:
> mysql_protocol.prototest [ pass ] 127885

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

Revision history for this message
Patrick Crews (patrick-crews) wrote :

Found innodb-semi-consistent to be lagging due to default=50 for innodb_lock_wait_timeout. Setting it to 2 = faster test : )

main.innodb-semi-consistent [ pass ] 6744 < - woot!
main.innodb-semi-consistent [ pass ] 102035

Changed in drizzle:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.