-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the Travis JS related tests #300
base: master
Are you sure you want to change the base?
Changes from all commits
e6b2903
ddf1a56
dc720a4
fd84d1c
a6998bc
d01a41b
0bbfaa1
12f6cb0
de44890
8f89cb0
db3014b
98bbeb2
dddcec8
554180a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,33 @@ | ||
language: python | ||
|
||
before_cache: | ||
- rm -f $HOME/.cache/pip/log/debug.log # erase log | ||
- rm -f $HOME/.cache/pip/log/debug.log # erase log | ||
|
||
cache: | ||
apt: true | ||
npm: true | ||
pip: true | ||
directories: | ||
- $HOME/.npm | ||
- $HOME/.cache/pip | ||
Comment on lines
10
to
12
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we still need this if we use Travis's built-in definitions? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Honestly I'm not sure. At one point caching was only available in the pro one unless you configured it yourself! I don't know if it dealt with such subtleties too, so I'm tempted to leave it given it doesn't really do any harm. |
||
|
||
before_install: | ||
#Switch node to the latest LTS version | ||
- if [ "$TASK" = "karma" -o "$TASK" = "lint" -o "$TASK" = "closure-compiler" ]; then nvm install lts/* && nvm use lts/*; fi | ||
|
||
install: | ||
- if [ "$TASK" = "nosetests" -o "$TASK" = "flake8" -o "$TASK" = "flake8-wip" ]; then pip install json-spec; fi | ||
- if [ "$TASK" = "karma" -o "$TASK" = "lint" -o "$TASK" = "closure-compiler" ]; then npm install -g grunt-cli; fi | ||
- if [ "$TASK" = "karma" -o "$TASK" = "lint" -o "$TASK" = "closure-compiler" ]; then npm install; fi | ||
- if [ "$TASK" = "karma" -o "$TASK" = "lint" -o "$TASK" = "closure-compiler" ]; then npm --verbose install -g grunt-cli; fi | ||
- if [ "$TASK" = "karma" -o "$TASK" = "lint" -o "$TASK" = "closure-compiler" ]; then grunt --version --verbose; fi | ||
- if [ "$TASK" = "karma" -o "$TASK" = "lint" -o "$TASK" = "closure-compiler" ]; then npm --verbose install; fi | ||
- if [ "$TASK" = "flake8" -o "$TASK" = "flake8-wip" ]; then pip install flake8; fi | ||
# If this causes SSL errors, then Sourceforge is probably in disaster recovery mode and needing Javascript. Could switch to a specific mirror, e.g. kent.dl.sourceforge.net | ||
- if [ "$TASK" = "pychecker" -o "$TASK" = "pychecker-wip" ]; then pip install http://sourceforge.net/projects/pychecker/files/pychecker/0.8.19/pychecker-0.8.19.tar.gz/download; fi | ||
- if [ "$TASK" = "codespell" ]; then pip install git+https://github.com/codespell-project/codespell.git; fi | ||
|
||
after_failure: | ||
- if [ -f /home/travis/.npm/_logs/*-debug.log ]; then cat /home/travis/.npm/_logs/*-debug.log; fi | ||
|
||
matrix: | ||
fast_finish: true | ||
include: | ||
|
@@ -27,7 +38,17 @@ matrix: | |
- os: linux | ||
dist: focal | ||
arch: arm64 | ||
env: TASK="karma" | ||
env: | ||
- TASK="karma" | ||
# Make Firefox headless | ||
- MOZ_HEADLESS=1 | ||
# Mozilla doesn't currently support nightly arm64 builds, so install via apt instead | ||
#addons: | ||
# firefox: latest | ||
addons: | ||
apt: | ||
packages: | ||
- firefox | ||
services: | ||
- xvfb | ||
- os: linux | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still needed when using Travis's built-in definitions for the cache?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly I'm not sure. At one point caching was only available in the pro one unless you configured it yourself! I don't know if it dealt with such subtleties too, so I'm tempted to leave it given it doesn't really do any harm.