MantisBT - CDash
View Issue Details
0015192CDash(No Category)public2014-10-03 07:392014-10-03 07:39
madtibo 
 
normalminorrandom
newopen 
LinuxDebian7.6
2.1 
 
0015192: SQL deadlock in ComputeTestTiming
I did nothing particular but got some SQL deadlock since 3 days in my nightly build.
It seems to finally succeed but it commits the tests 3 times. Thus instead of 83 failed and 2242 succeeded I got 249 failed and 6726 succeeded.

I had some traces in models/build.php and will check which of the UPDATE is causing the deadlock (since it seems that a deadlock comes from an UPDATE).

But maybe you have a clue what is suddenly causing this behaviour.
Or at least there might exist a way to not commit 3 times the tests in case of deadlocks.
[2014-09-11T09:46:33][INFO][pid=5446](addbuildgroup): Build #174 removed manualy
[2014-10-01T23:36:19][ERROR][pid=27399](Build:ComputeTestTiming): SQL error: Deadlock found when trying to get lock; try restarting transaction
[2014-10-02T02:57:11][ERROR][pid=28336](Build:ComputeTestTiming): SQL error: Deadlock found when trying to get lock; try restarting transaction
[2014-10-02T02:57:16][ERROR][pid=28336](Build:ComputeTestTiming): SQL error: Deadlock found when trying to get lock; try restarting transaction
[2014-10-02T23:34:15][ERROR][pid=20524](Build:ComputeTestTiming): SQL error: Deadlock found when trying to get lock; try restarting transaction
[2014-10-02T23:36:23][ERROR][pid=25674](Build:ComputeTestTiming): SQL error: Deadlock found when trying to get lock; try restarting transaction
[2014-10-03T02:57:06][ERROR][pid=27399](Build:ComputeTestTiming): SQL error: Deadlock found when trying to get lock; try restarting transaction
[2014-10-03T02:57:12][ERROR][pid=27399](Build:ComputeTestTiming): SQL error: Deadlock found when trying to get lock; try restarting transaction
No tags attached.
Issue History
2014-10-03 07:39madtiboNew Issue

There are no notes attached to this issue.