Getting Unexpected Exit Code 139 (specific versions, usually beta) about unity-test-runner

[DooblyNoobly]

I'm getting the exact problem with our tests: https://github.com/unitystation/unitystation/actions

Here is our test config: https://github.com/unitystation/unitystation/blob/develop/.github/workflows/test.yml

We also just upgraded from Unity 2019.2 to 2019.3. It would work most of the time when we were on 2019.2 but every now and then would throw the urinary error:

/steps/run_tests.sh: line 164: [: =: unary operator expected /steps/run_tests.sh: line 182: [: -gt: unary operator expected

Now after upgrading to 2019.3 it fails with that error all the time

[webbertakken]

Hey @pablothedolphin adn thanks for reporting your issue!

Could you also show your workflow configuration for your test job?

[pablothedolphin]

Here's my action script:

Thanks for the quick response @webbertakken ! Here it is:

name: Run Unit Tests

on:
  pull_request: {}
  push: { branches: [master] }

env:
  UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}

jobs:
  testAllModes:
    name: Test in ${{ matrix.testMode }} on version ${{ matrix.unityVersion }}
    runs-on: ubuntu-latest
    strategy:
      fail-fast: false
      matrix:
        projectPath:
          - Test-Project
        unityVersion:
          - 2019.3.6f1
          - 2020.1.0b4
        testMode:
          - editmode
          - playmode
    steps:
      - uses: actions/checkout@v2
        with:
          lfs: true
      - uses: actions/[email protected]
        with:
          path: ${{ matrix.projectPath }}/Library
          key: Library-${{ matrix.projectPath }}
          restore-keys: |
            Library-
      - uses: webbertakken/[email protected]
        id: tests
        with:
          projectPath: ${{ matrix.projectPath }}
          unityVersion: ${{ matrix.unityVersion }}
          testMode: ${{ matrix.testMode }}
          artifactsPath: ${{ matrix.testMode }}-artifacts
      - uses: actions/upload-artifact@v1
        with:
          name: Test results for ${{ matrix.testMode }}
          path: ${{ steps.tests.outputs.artifactsPath }}

My best guess is that the license activates fine but it fails to open the editor / the editor is crashing somehow.

[webbertakken]

Hmm it doesn't really become clear from these logs what's going on.

You're right about that it looks like the license activates but then the editor crashes. Note that activating already happens within the editor itself. So it's when trying to run your tests that it crashes.

Possibly a permission issue. Otherwise perhaps a misconfiguration of test assembly files. Either way we need to find a better way to get logs out of unity.

[webbertakken]

Good to know it doesn't always happen and that there seems to be a difference between Unity versions. I'd say that rules out misconfiguration of test assembly files.

I doubt the unary operator being the reason for the actual failure, and still think the failure is silent. On the runs where it doesn't fail, does it also give you the errors about unary operator?

[DooblyNoobly]

So this is what those logs look like in a test that passes:

2020-04-06T21:45:55.5686712Z /steps/run_tests.sh: line 109: [: =: unary operator expected
2020-04-06T21:45:55.5687144Z /steps/run_tests.sh: line 164: [: =: unary operator expected
2020-04-06T21:45:55.5687908Z /steps/run_tests.sh: line 182: [: -gt: unary operator expected
2020-04-06T21:45:55.7803486Z ##[group]Run actions/setup-dotnet@v1```

So I guess yeah it does it on tests that have passed as well

[webbertakken]

Yea so it is really about Unity not giving us enough information about what's going on.

I think we need to get more information out of either unity or the test script specifically.

[webbertakken]

Duplicate of https://github.com/webbertakken/unity-actions/issues/70#issuecomment-637817909

This issue can be resolved by using stable, non-beta versions.

[webbertakken]

See also https://github.com/game-ci/unity-actions/issues/84