(CC'ing the internals list) I looked at some of the reports. Most of them are timeouts. Many with --no-baseline --no-ion JIT flags, so it's likely unrelated to the JITs.
I glanced at the commit log before this started, here are some bugs that seem related at a quick glance: Bug 941805 - Make the pool of JS workers be per process rather than per runtime (maybe there's a race or deadlock somewhere?) Bug 965745 - Always patch loop backedges in Ion if interrupt flag is set (a bug there could cause issues like this but since it also happens without the JITs it's unlikely). Brian/Bill, could this be bug 941805? Maybe something in NSPR? Thanks, Jan On Tue, Feb 11, 2014 at 1:50 PM, Ryan VanderMeulen <[email protected]> wrote: > Recently, we've seen a very big spike in Windows jit-test failures. From > what I can tell, it started around Thursday last week. Can we please get > someone on the JS team to look into this soon? > > JS intermittents filed in the last week: > https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=9412412&chfieldto=Now&query_format=advanced&chfield=[Bug%20creation]&chfieldfrom=-168h&component=JavaScript&component=JavaScript%20Engine&component=JavaScript%20Engine%3A%20JIT&component=JavaScript%3A%20GC&component=JavaScript%3A%20Internationalization%20API&component=JavaScript%3A%20Standard%20Library > > Thanks! > > -Ryan > _______________________________________________ > dev-tech-js-engine mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-js-engine _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
