http://drupal.org/project/date/testing-status currently says "Waiting for results."
The test is http://qa.drupal.org/pifr/test/200603

Quoting jthorson from IRC:

That's a xmlrpc communication issue ... haven't got to the bottom of it. But if you look on qa.d.o, the test actually completes successfully (both simpletest and coder)

Comments

jthorson’s picture

jthorson commented

One possible (elaborate) solution to solve this:

We create a new key in the PIFT array that gets sent over to qa.d.o, called 'update'. Inside this key, we send an array of tests which are currently in the 'sent' state; representing the list of outstanding tests from PIFT's perspective.

On the PIFR side, we do a query on pifr_test, using the received test_id's from the 'update' key. If any of the test_ids are not in the 'queued' state, PIFR adds them to a response array, with the appropriate status (postponed, pass, fail, etc), and fires them back to PIFT.

Upon reception, PIFT updates it's own database with the proper values.

This way, the two db's are able to stay in sync, even when the communication between them fails.

(Of course, it sure would be nice to know why the communication between them fails in the first place!!!)

jthorson’s picture

jthorson commented

I suspect this will happen if the test is cancelled, as I just ran into it during PIFT porting. Need to re-visit ... just not now. Adding note as a reminder.

isntall’s picture

isntall commented
Project: Drupal.org Testbots » DrupalCI: Test Runner
Issue summary: View changes
jthorson’s picture

jthorson commented
Project: DrupalCI: Test Runner » Project Issue File Review
Version: » 6.x-3.x-dev

This is specific to qa.d.o, and does not carry forward to DrupalCI.