forgetest1
/
antlr
forked from jasder/antlr
1
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity
antlr/.travis/run-tests-swift.sh

42 lines
1.2 KiB
Bash
Raw Normal View History

merge old and new travis; improve so it runs C++ on osx; update BaseSwiftTest so it mirrors other targets; remove unneeded dep in pom to some json stuff
2016-11-21 11:50:54 +08:00
#!/bin/bash
Run the Swift runtime unit tests during the Travis run. These are the unit tests that are written in Swift, not the more in-depth runtime-testsuite tests (we were always running those). I don't know why JAVA_HOME isn't set during run-tests-swift.sh, but it isn't. Set it, since runtime/Swift/boot.py expects it as part of the parser generation.
2017-11-02 15:21:53 +08:00
set -euo pipefail
fix linker issue on travis ubuntu
2017-05-14 08:00:27 +08:00
# linux specific setup, those setup have to be
# here since environment variables doesn't pass
# across scripts
if [ $TRAVIS_OS_NAME == "linux" ]; then
[Swift] Migrate Swift runtime to Swift 5. This switches from using the deprecated hashValue to hash(into:). It also switches from using index to firstIndex (matching the change in the standard library). In the test template, we switch to using String directly instead of String.characters. This also switches all the Travis macOS tests to use the Xcode 10.2 / Mojave image and changes the Linux Swift tests to download Swift 5.0.1.
2019-03-29 06:24:27 +08:00
export SWIFT_VERSION=swift-5.0.1
Move Travis tests to Swift 4.2 and Xcode 10.1. Move Travis Swift, .NET, and C++ macOS tests from Xcode 9 to Xcode 10.1. Move Travis Linux Swift tests from Trusty to Xenial and to Swift 4.2.1. Remove the dirname call when setting JAVA_HOME, it seems to be incorrect. Print the JAVA_HOME that Travis ends up with. Moving to Xcode 10.1 / Swift 4.2 exposes the issue discussed in #2372 so this cset will fail automated tests without the relevant fixes.
2018-11-08 05:11:06 +08:00
export SWIFT_HOME=$(pwd)/swift/$SWIFT_VERSION-RELEASE-ubuntu16.04/usr/bin/
fix linker issue on travis ubuntu
2017-05-14 08:00:27 +08:00
export PATH=$SWIFT_HOME:$PATH
# download swift
mkdir swift
Move Travis tests to Swift 4.2 and Xcode 10.1. Move Travis Swift, .NET, and C++ macOS tests from Xcode 9 to Xcode 10.1. Move Travis Linux Swift tests from Trusty to Xenial and to Swift 4.2.1. Remove the dirname call when setting JAVA_HOME, it seems to be incorrect. Print the JAVA_HOME that Travis ends up with. Moving to Xcode 10.1 / Swift 4.2 exposes the issue discussed in #2372 so this cset will fail automated tests without the relevant fixes.
2018-11-08 05:11:06 +08:00
curl https://swift.org/builds/$SWIFT_VERSION-release/ubuntu1604/$SWIFT_VERSION-RELEASE/$SWIFT_VERSION-RELEASE-ubuntu16.04.tar.gz -s | tar xz -C swift &> /dev/null
fix linker issue on travis ubuntu
2017-05-14 08:00:27 +08:00
fi
Run the Swift runtime unit tests during the Travis run. These are the unit tests that are written in Swift, not the more in-depth runtime-testsuite tests (we were always running those). I don't know why JAVA_HOME isn't set during run-tests-swift.sh, but it isn't. Set it, since runtime/Swift/boot.py expects it as part of the parser generation.
2017-11-02 15:21:53 +08:00
if [ -z "${JAVA_HOME-}" ]
then
Move Travis tests to Swift 4.2 and Xcode 10.1. Move Travis Swift, .NET, and C++ macOS tests from Xcode 9 to Xcode 10.1. Move Travis Linux Swift tests from Trusty to Xenial and to Swift 4.2.1. Remove the dirname call when setting JAVA_HOME, it seems to be incorrect. Print the JAVA_HOME that Travis ends up with. Moving to Xcode 10.1 / Swift 4.2 exposes the issue discussed in #2372 so this cset will fail automated tests without the relevant fixes.
2018-11-08 05:11:06 +08:00
export JAVA_HOME="$(java -XshowSettings:properties -version 2>&1 |
grep 'java\.home' | awk '{ print $3 }')"
echo "export JAVA_HOME=$JAVA_HOME"
Run the Swift runtime unit tests during the Travis run. These are the unit tests that are written in Swift, not the more in-depth runtime-testsuite tests (we were always running those). I don't know why JAVA_HOME isn't set during run-tests-swift.sh, but it isn't. Set it, since runtime/Swift/boot.py expects it as part of the parser generation.
2017-11-02 15:21:53 +08:00
fi
fix linker issue on travis ubuntu
2017-05-14 08:00:27 +08:00
# check swift
swift --version
swift build --version
Run the Swift runtime unit tests during the Travis run. These are the unit tests that are written in Swift, not the more in-depth runtime-testsuite tests (we were always running those). I don't know why JAVA_HOME isn't set during run-tests-swift.sh, but it isn't. Set it, since runtime/Swift/boot.py expects it as part of the parser generation.
2017-11-02 15:21:53 +08:00
pushd ../runtime/Swift
./boot.py --test
popd
categorise tests to fix Travis timeout, fix script
2017-06-27 01:47:01 +08:00
if [ $GROUP == "LEXER" ]; then
mvn -q -Dgroups="org.antlr.v4.test.runtime.category.LexerTests" -Dtest=swift.* test
elif [ $GROUP == "PARSER" ]; then
mvn -q -Dgroups="org.antlr.v4.test.runtime.category.ParserTests" -Dtest=swift.* test
elif [ $GROUP == "RECURSION" ]; then
Fix typo and rebalance
2017-06-27 07:43:59 +08:00
mvn -q -Dgroups="org.antlr.v4.test.runtime.category.LeftRecursionTests" -Dtest=swift.* test
categorise tests to fix Travis timeout, fix script
2017-06-27 01:47:01 +08:00
else
fix failing build
2017-06-28 20:40:16 +08:00
mvn -q -Dtest=swift.* test
categorise tests to fix Travis timeout
2017-06-27 00:50:49 +08:00
fi