#699 is passing every core patch with 11 assertions (as opposed to the normal 35k or so). Examples:
http://qa.drupal.org/pifr/test/245519
http://qa.drupal.org/pifr/test/245539
http://qa.drupal.org/pifr/test/245504

Other bots do not seem to be affected:
http://qa.drupal.org/pifr/test/245524

Because it is so fast to test 11 assertions, it is also burning through everything in the queue. All of these will need to be retested. :(

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Fixed

Sadly, it somehow got set to "shortcut core tests", probably for a quick reconfirmation. I fixed it.

xjm’s picture

xjm
she/her
Primary language English
commented

Is there a way to re-test everything it passed in bulk? There are lots and lots of patches that didn't get tested but will be showing up green...

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Oh so sad.

It's easy enough to find them (assuming we know a start time). http://qa.drupal.org/pifr/log/client/699 shows them all... but I think the retest has to be initiated one by one, by clicking on the patch there and Tools->retest.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

I took a look to see if we could do this with VBO, but no dice. There is no operation that works. We definitely need to get that into a new version.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Opened #1503000: VBO actions for tests

xjm’s picture

xjm
she/her
Primary language English
commented

I guess I'll start clicking... I found what appear to be the oldest tests with 11 assertions.

Edit: Done clicking.

jthorson’s picture

jthorson commented

xjm: Omfg. So sorry. :(

We had three bots tied up last night with tests that were just looping (one had been testing the same patch for 36 hours). To try and keep the queue moving, I shortcutted the confirmation process, and my final 'submit' click must not have made it to the server for processing.

As a side note, this is yet another error that would have been avoided if the new PIFR release candidate (which has been ready for weeks) had been rolled out to qa.d.o; as it contains a patch to allow shortcutting confirmation without affecting other tests.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Updated issue summary.