Antonio Scandurra 6d9f6befd2 Increase timeout for atom-application.test.js on CI ... On Azure and Travis, we recently started observing a few test failures in atom-application.test.js. After staring at those tests for a bit, it doesn't seem like they are failing due to a race condition. Instead, it is possible that these tests are simply timing out due to CI containers sometimes being overloaded and, thus, slower. I tested this hypothesis locally by running tests on a VM while stress-testing the host machine. Tests would eventually have passed, but they timed out before having the chance to do so. This commit increases the timeout on CI to 10 seconds for `AtomApplication` tests in an attempt to fix the spurious failures we were observing. This is similar to what we've historically done for renderer process tests (see 7faea50190/spec/spec-helper.coffee (L50)).		2019-06-13 16:36:55 +02:00
..
atom-application.test.js	Increase timeout for atom-application.test.js on CI	2019-06-13 16:36:55 +02:00
atom-window.test.js	Don't symlink compile-cache folder in AtomWindow tests	2019-06-06 17:11:01 +02:00
file-recovery-service.test.js	Reformat all JS files using prettier	2019-05-31 18:33:56 +02:00
mocha-test-runner.js	Reformat all JS files using prettier	2019-05-31 18:33:56 +02:00
parse-command-line.test.js	Reformat all JS files using prettier	2019-05-31 18:33:56 +02:00