I'm trying to track down bug 520321, but I'm unable to reproduce the regression by running Talos on a local Leopard machine. The best way to debug this would be to have access to one of the Talos instances that can or is reproducing the regression, such that I can back out portions of the patch and re-run the tests.
Can you reproduce this on try talos? Whats worked well in the past is: - have the developer attempt to reproduce the problem on Try Server talos - as soon as you can reproduce, file bug to RelEng (or comment here in this one) - we will pull that specific slave out of circulation for you to examine - whenever you are done, we'll reset the slave, and put it back into the Try Server talos pool. Seem reasonable?
dvandr: also, fyi, the version of standalone talos was recently refreshed. We'd updated changes into production talos, but had forgotten to make matching updates to standalone talos. This was fixed on 16th sept. Please confirm that your attempts at standalone talos were done using this newly refreshed standalone version.
A box has already been pulled from the try pool for mstange, either dvander and mstange can work with the box together or it can be passed on after mstange is done. See bug 520512.
I'm done with the machine now; contact me on IRC when you want it.
we've been able to reproduce this on some laptops