checkout:
  post:
    - git submodule update --init

dependencies:
  pre:
    # https://github.com/meteor/docs/blob/version-NEXT/long-form/file-change-watcher-efficiency.md
    - echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
  cache_directories:
    - "dev_bundle"
    - ".meteor"
    - ".babel-cache"
  override:
    # shouldn't take longer than 10 minutes
    - METEOR_PRETTY_OUTPUT=0 ./meteor --get-ready:
        timeout: 600

test:
  override:
    - ./scripts/ci.sh :
        parallel: true
        timeout: 1200

checkout:
  post:
    - git submodule update --init

dependencies:
  pre:
    # https://github.com/meteor/docs/blob/version-NEXT/long-form/file-change-watcher-efficiency.md
    - echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
  cache_directories:
    - "dev_bundle"
    - ".meteor"
    - ".babel-cache"
  override:
    # shouldn't take longer than 10 minutes
    - METEOR_PRETTY_OUTPUT=0 METEOR_DISABLE_OPTIMISTIC_CACHING=1 ./meteor --get-ready:
        timeout: 600

test:
  override:
    - ./scripts/ci.sh :
        parallel: true
        timeout: 1200

Disable optimistic caching for `meteor --get-ready` on Circle CI.
Disable optimistic caching for `meteor --get-ready` on Circle CI.

We (@abernix and I) suspect the intermittent "died unexpectedly" failures
of `meteor --get-ready` on Circle CI are due to hitting their (low) limit
on the maximum number of open files.

Although optimistic caching speeds up rebuilds considerably, it doesn't do
much for initial builds, and it definitely keeps more files open.
Disabling it here seems worth a try.
