On 1 Jun 2011, at 19:21, Paul Davis wrote: > This usually indicates that something broked on the server. I've only > seen it in corner cases where I segfault in a NIF or similar. Did you > check if couch was still running?
Couch was running, and the tests afterwards all passed. >> auth_cache fails >> >> assertion misses_after == misses_before +1 failed >> >> assertion hits_after == hits_before failed >> > > This is related to browser cache. Command-Shift-R and the cache sweep > button usually fixes it. Should the tests work around this? >> cookie_auth fails >> >> "error": "file_exists" >> > > Didn't we just fix this? Evidently not. ;) >> Gonna give this -1 until we fix the unit tests. >> >> I wonder whether anyone else runs the unit tests at all, sometimes! ;) > > I ran them on Chrome and they passed just fine. Perhaps its a FF issue > that no-one has noticed yet. Also, you don't have Firebug turned on do > you? That can screw with things. I don't even have it installed! Just ran the tests in Chrome and they all pass. What gives?
