Test runner fails when using gitlab-ci


I’ve set up a CI system for my project with gitlab-ci, using this repository as a template. I run the following batch script for the tests:

"Unity.exe" ^
  -projectPath "%cd%" ^
  -batchmode ^
  -runTests ^
  -testPlatform editmode ^
  -testResults "%cd%\editmode-results.xml" ^
  -logfile testlog.log ^
  || goto :error

echo "Tests successful!""
exit /b 0

echo Failed with error #%errorlevel%.
exit /b %errorlevel%

The CI runner is running on my own computer on the same user, and when I manually go to the runner directory and run the scripts they are successful. However, when gitlab-ci does it, it fails with error code 255. The terminal shows nothing except for the command and the “Failed with error #255” message, and the result xml shows all the tests passed both when running local and on gitlab-ci. The log files (testlog.log) are almost identical except for the gitlab-ci one having two lines like this:

Symbol file LoadedFromMemory doesn't match image D:\Gitlab-Runner\builds\e4Y8wNDA\1\algoryx\external\unity-project\AGMSim\Library\PackageCache\com.unity.ext.nunit@1.0.0\net35\unity-custom\nunit.framework.dll

and the local one having these lines at the end:

Checking for leaked weakptr:
  Found no leaked weakptrs.

Anyone have any ideas what this could be about or how to investigate further? Another thing worth mentioning is that I have another job that builds the application in a similar way using the Unity CLI and it always works fine with no error messages.

I’m attaching the two log files (I had to change the file extensions to be able to upload them).

Thanks in advance,

5018540–491525–testlog_local.txt (234 KB)
5018540–491528–testlog_gitlab-ci.txt (234 KB)

I would also try to add -quit and -nographics to the args u are using to launch Unity with.

Thanks for the answer!

Adding the -nographics flag made no difference, and adding the -quit flag makes it so the application always exits with exit status 0, even when tests fail, and no xml file is generated.

I also tried using the -runEditorTests flag instead of -runTests, but that didn’t change anything either.

I think I’ll avoid checking the return status and just try parsing the xml file somehow instead…

When running Unity.exe like that, does the process block until Unity completes or does it exit immediately?
Also, do u have a chance to test the same on a MacOS based machine? (if that is even supported by gitlab-CI)

It blocks, both when I run it manually from a command prompt, and when the CI runs it. The command takes about a minute since it needs to regenerate the Library folder.

I haven’t tried it on a Mac machine, but I could give it a try.

any updates? were u able to resolve this issue ?

Yes and no. I did the workaround I mentioned above, writing a Python script that parses the test log xml file, and it works fine. Since it worked I haven’t researched the issue further.

For reference, here is the Python script I’m using:

import sys
import xml.etree.ElementTree as ET

tree = ET.parse(sys.argv[1])
root = tree.getroot()

num_failed = root.attrib["failed"]
num_passed = root.attrib["passed"]
num_inconclusive = root.attrib["inconclusive"]
num_skipped = root.attrib["skipped"]
print("Number of tests passed: " + num_passed)
print("Number of tests failed: " + num_failed)
print("Number of inconclusive tests: " + num_inconclusive)
print("Number of skipped tests: " + num_skipped)
if root.attrib["result"] == "Passed":
elif int(num_failed) > 0:

This is my .gitlab-ci.yml

  - editmodetests
  - playmodetests
  - build
  - deploy
  stage: editmodetests
  script: "C:\\'Program Files'\\Unity\\Hub\\Editor\\2019.3.0b4\\Editor\\Unity.exe \
  -batchmode \
  -projectPath . \
  -runTests -testPlatform editmode \
  -logFile \
  -testResults ./TestResults/edit-tests.xml"
    - unity
  stage: playmodetests
  script: "C:\\'Program Files'\\Unity\\Hub\\Editor\\2019.3.0b4\\Editor\\Unity.exe \
  -batchmode \
  -projectPath . \
  -runTests -testPlatform playmode \
  -logFile \
  -testResults ./TestResults/play-tests.xml"
    - unity
  stage: build
  script: echo 'Building...'
    - unity
  stage: deploy
  script: echo 'Deploying...'
    - unity

It works fine :wink:


What is your environment? I cant run tests from gitlab on mac

Have another issue when run gitlab runner from git lab. When execute this command locally everything works ok.

/Applications/Unity/Hub/Editor/2019.2.19f1/Unity.app/Contents/MacOS/Unity -batchmode -projectPath .  -runTests -testPlatform editmode -testResults ./editmode-unit-tests.xml
2020-02-13 01:25:35.521 Unity[2402:29587] Color LCD preferred device: Intel Iris Pro Graphics (low power)
2020-02-13 01:25:35.521 Unity[2402:29587] Metal devices available: 2
2020-02-13 01:25:35.521 Unity[2402:29587] 0: Intel Iris Pro Graphics (low power)
2020-02-13 01:25:35.521 Unity[2402:29587] 1: NVIDIA GeForce GT 750M (high power)
2020-02-13 01:25:35.522 Unity[2402:29587] Using device NVIDIA GeForce GT 750M (high power)

Aborting batchmode due to failure:
Scripts have compiler errors.

Native stacktrace:

    0   libmonobdwgc-2.0.dylib              0x0000000142d46a22 mono_handle_native_crash + 242
    1   libmonobdwgc-2.0.dylib              0x0000000142ca7ce1 mono_sigsegv_signal_handler + 220
    2   libsystem_platform.dylib            0x00007fff69ab542d _sigtramp + 29
    3   ???                                 0x0000000000000000 0x0 + 0
    4   Unity                               0x00000001054b7af8 _ZN12AudioManager14systemCallbackEP11FMOD_SYSTEM24FMOD_SYSTEM_CALLBACKTYPEPvS3_ + 424
    5   Unity                               0x000000010964ebaf _ZN4FMOD6Thread8callbackEPv + 175
    6   libsystem_pthread.dylib             0x00007fff69ac0e65 _pthread_start + 148
    7   libsystem_pthread.dylib             0x00007fff69abc83b thread_start + 15

Debug info from gdb:

(lldb) command source -s 0 '/tmp/mono-gdb-commands.aHzSb7'
Executing commands in '/tmp/mono-gdb-commands.aHzSb7'.
(lldb) process attach --pid 2402
error: attach failed: Error 1
ERROR: Job failed: exit status 1

Did you find a fix for this? I'm getting the exact same stacktrace when building for Android on GitLab with Unity 2019.2.21 (No tests running, and iOS builds from the same project does not have any issues).