From f339dec5ae02c2ef12679d5edcf0a623ff70641f Mon Sep 17 00:00:00 2001 From: Ben Newman Date: Tue, 16 May 2017 14:55:20 -0400 Subject: [PATCH] Try not running a full meteor --get-ready before Circle CI tests. In the ongoing struggle with Circle CI-specific test failures, the preparatory `meteor --get-ready` has been a consistent point of failure, before any real tests have the chance to run. Using a lighter-weight command (meteor --help) that still does most of what --get-ready did seems worth a try, though it might just defer memory-intensive work until later, so we'll have to see what happens. --- circle.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/circle.yml b/circle.yml index 0241b50520..d7f983e499 100644 --- a/circle.yml +++ b/circle.yml @@ -13,9 +13,9 @@ dependencies: - ".meteor" - ".babel-cache" override: - # shouldn't take longer than 10 minutes - - ./meteor --get-ready: - timeout: 600 + # shouldn't take longer than 5 minutes + - ./meteor --help: + timeout: 300 environment: METEOR_PRETTY_OUTPUT: 0 METEOR_DISABLE_OPTIMISTIC_CACHING: 1