Comment 2 for bug 671335

I see it very frequently, several times in the average day of development. It costs me considerable time and energy, since interrupting the broken (and so generally pointless) ongoing test run seems to make the error come back next time.

Perhaps I'm hitting this because I do a lot of my work in a feature branch and so I'm switching back and forth between different schema versions, code versions, and sourcecode setups.