Started by an SCM change Building in workspace /var/lib/jenkins/jobs/StdLib2/workspace > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/wurstscript/wurstStdlib2.git # timeout=10 Fetching upstream changes from https://github.com/wurstscript/wurstStdlib2.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/wurstscript/wurstStdlib2.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision 0e24b8b91f999746a235f6c69c7dcde75048e3da (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0e24b8b91f999746a235f6c69c7dcde75048e3da > git rev-list ebf445a6126dd459bc441b3789920dbd421fda3c # timeout=10 [workspace] $ /bin/sh -xe /tmp/hudson4225814754696498180.sh + java -jar ../../Wurst/workspace/downloads/Wurstpack/wurstscript/wurstscript.jar ../../Wurst/workspace/downloads/Wurstpack/wurstscript/common.j ../../Wurst/workspace/downloads/Wurstpack/wurstscript/blizzard.j ./ -runcompiletimefunctions -runtests Running tests Running test .. success! Running test .. success! Running test .. success! Running test .. FAILED Running test .. success! Running test .. success! Running test .. success! Running test .. success! Running test .. success! Running test .. success! Running test .. success! Running test .. success! Running test .. success! Tests succeeded: 12/13 >> The following tests failed: test failed: assertion failed ... when calling assertTrue(false) in Colors.wurst:160 ... when calling testColors() in Colors.wurst:158 Finished running tests compilation finished (errors: 1, warnings: 9) Error in File Colors.wurst line 158: test failed: assertion failed Build step 'Execute shell' marked build as failure Sending e-mails to: peter.peq@gmail.com frotty@sunayama.de Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: FAILURE