There are two issues fixed: - With the latest Nim version sometimes the files `<package_name>_<some_number>.nims`' generated on `nim install` contain warning for unused imports which causes the test "can validate package structure (#144)" to fail, because it was searching for the word "warning" in the output. - On Windows Subsystem for Linux, when an import starts sometimes with a lowercase, and sometimes with an uppercase, for example `import uri` and `import Uri`, this causes Nim to create and compile both `stdlib_uri.nim.c` and `stdlib_Uri.nim.c` and to fail on the linking step, because of the same symbols are being redefined. Also the Travis CI build script is changed to test against currently the latest working Nim version 212ae2f. Related to #680
35 lines
696 B
YAML
35 lines
696 B
YAML
os:
|
|
- linux
|
|
- osx
|
|
|
|
language: c
|
|
|
|
env:
|
|
- BRANCH=0.19.6
|
|
- BRANCH=0.20.2
|
|
# This is the latest working Nim version against which Nimble is being tested
|
|
- BRANCH=#212ae2f1257628bd5d1760593ce0a1bad768831a
|
|
|
|
cache:
|
|
directories:
|
|
- "$HOME/.choosenim/toolchains/nim-0.19.6"
|
|
- "$HOME/.choosenim/toolchains/nim-0.20.2"
|
|
|
|
install:
|
|
- export CHOOSENIM_CHOOSE_VERSION=$BRANCH
|
|
- |
|
|
curl https://nim-lang.org/choosenim/init.sh -sSf > init.sh
|
|
sh init.sh -y
|
|
|
|
before_script:
|
|
- export CHOOSENIM_NO_ANALYTICS=1
|
|
- export PATH=$HOME/.nimble/bin:$PATH
|
|
|
|
script:
|
|
- cd tests
|
|
- nim c -r tester
|
|
- cd ..
|
|
- ./src/nimble install -y
|
|
|
|
notifications:
|
|
irc: "chat.freenode.net#nimbuild"
|