Ticket #784 (new defect )

Opened 4 years ago

Last modified 3 years ago

adbapi tests intermittently fail with TimeoutError

Reported by: warner Assigned to: davep
Type: defect Priority: high
Milestone: Component:
Keywords: core Cc: spiv, davep, warner
Branch: Author:
Launchpad Bug:

Attachments

Change History

  2004-11-09 02:33:01+00:00 changed by warner 

The database tests (test_adbapi, test_reflector) have been failing consistently
against the gtk2 reactor, and most of the time against the gtk(1) reactor.
The specific example I'm seeing is:
 ./bin/trial -v -r gtk2 twisted.test.test_adbapi.SQLiteADBAPITestCase.testPool
Which gives me a timeout error on an unloaded system, while it's waiting for a
simple CREATE TABLE operation to complete. Worse yet, trial hangs before
exiting, after the "FAILED (errors=1)" message.
I'm thinking this is a threading issue, espcially because of the exit-hang
(waiting for a thread from the pool to exit?). The adbapi code creates and
eventually shuts down a thread pool, maybe this is interacting badly with the
gtk2 event loop?. Unfortunately I didn't see anything helpful in test.log .

  2004-11-20 17:52:41+00:00 changed by radix 

this is happening on SelectReactor too, according to buildbot. It's failing in
testPool, but not during schema creation; instead, while it's trying to fill it
with data.

  2004-12-07 06:08:43+00:00 changed by glyph 

Still technically t.e's maintainer :)

  2004-12-12 05:42:19+00:00 changed by davep 

I'm still here, I'm just really lazy :)
I was seeing some other tests fail with TimeoutErrors
just because they were really slow, these are fixed.
I also removed some deprecation warnings in the tests.
But, I can't reproduce the error below with python2.3
and debian unstable. How can I log into the test machine
and reproduce this?

  2004-12-13 03:31:29+00:00 changed by warner 

Log into pyr, then from there log into the sid-chroot (which listens on port
9022, but only on the loopback interface). I don't know how the passwd files
are managed, and a casual grep suggests you don't yet have an account in the
chroot, so you'll have to get someone with root to set that up for you.
Once there, just run the command as displayed by the build log (python2.3
./bin/trial etc etc). If you want to take a look at the buildslave's working
directory, it's in ~buildbot/BuildBot/slave/full2.3/ (or, from outside the
chroot, /sid-chroot/home/buildbot/BuildBot/slave/).

  2005-01-13 19:07:03+00:00 changed by spiv 

Is this the same as #859?

  2005-07-16 08:10:47+00:00 changed by warner 

FYI, this issue is still present. The most recent test failures occurred on the
2.4 builder, with the log available here:
http://twistedmatrix.com/buildbot/full-2.4/builds/466/shell/2
(replace the trailing '2' with '0' or '1' to get at the other logs for that build)
Note: See TracTickets for help on using tickets.