Rosella followed up with a correct observation that the fails might have been related to her patch and put it into workflow-1 state.
Patch 34 was pushed, and got lucky and passed check and was approved to gate.
Unfortunately at the 35% race rate, it means this was just litterally winning a coin flip. We got the 42% chance that it would pass both times (0.65^2).
Probably in future it would be better to run some manual rechecks on a patch like this preemptively to attempt to trigger the failure when it's been known to trip things in the past.
It's pretty clear that 243808 is the fix. If you look back on the Jenkins fails for https:/ /review. openstack. org/#/c/ 164880/ this was actually triggered in Patch Set 33: http:// logs.openstack. org/80/ 164880/ 33/gate/ gate-tempest- dsvm-neutron- full/56c541a/ console. html.gz# _2015-10- 21_19_57_ 34_141
Which blocked it from landing in the gate.
Then YAMAMOTO Takashi did a recheck to rerun the tests to land it.
It failed again on check - http:// logs.openstack. org/80/ 164880/ 33/check/ gate-tempest- dsvm-neutron- full/4e68240/ console. html.gz# _2015-10- 22_02_12_ 35_331
Rosella followed up with a correct observation that the fails might have been related to her patch and put it into workflow-1 state.
Patch 34 was pushed, and got lucky and passed check and was approved to gate.
Unfortunately at the 35% race rate, it means this was just litterally winning a coin flip. We got the 42% chance that it would pass both times (0.65^2).
Probably in future it would be better to run some manual rechecks on a patch like this preemptively to attempt to trigger the failure when it's been known to trip things in the past.