The Node Ownership project 7.x-1.x-dev was constantly retesting, starting over and over every minute. This had affected two different testbots.

Since it didn't even appear that this project was enabled for testing (nothing showed in the automated testing tab, and it wasn't enabled under "issues", I just deleted the tests on d.o

mysql> select * from pift_test where id=1487694;
+---------+------+---------+--------+--------------------------------------------------------------------------------------------------------------------+-------------+
| test_id | type | id      | status | message                                                                                                            | last_tested |
+---------+------+---------+--------+--------------------------------------------------------------------------------------------------------------------+-------------+
|       0 |    1 | 1487694 |      1 | NULL                                                                                                               |           0 | 
|  247204 |    1 | 1487694 |      4 | PASSED: [[Coder]]: [Code review] 57 minor(s), 7 critical(s), and 19 normal(s); [[SimpleTest]]: [MySQL] 0 pass(es). |  1334199937 | 
+---------+------+---------+--------+--------------------------------------------------------------------------------------------------------------------+-------------+
2 rows in set (0.10 sec)


mysql> delete from pift_test where id=1487694;
Query OK, 2 rows affected (0.13 sec)

Comments

rfay’s picture

I had to fiddle on qa to get it stopped as well. Not sure what was going on.

jthorson’s picture

Saw this earlier on a different project ... symptom was a repeated 'Test requeued by client request' entry in the log file. Never sorted out the actual root cause, but believe it shared the the 'duplicate test entry' symptom.

This duplicate test entry was also seen in #1472722: "Re-test request ignored because test is already queued.".

There must be some sort of scenario which causes the duplicate (and errored) test entries to be committed ... perhaps a race condition when a test is accidently double-submitted, resulting in both records being added to the database? In any case, the tests with test_id of '0' should not persist over the long term.

jthorson’s picture

Status: Active » Postponed

Possible dupe of #1501962: 'Test reset by client request' loops on tests..

Haven't seen again, but will keep around for tracking purposes.

isntall’s picture

Status: Postponed » Closed (won't fix)