Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Voting for the Unity Awards are OPEN! We’re looking to celebrate creators across games, industry, film, and many more categories. Cast your vote now for all categories
    Dismiss Notice
  3. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice The 15th Unity Awards Unite 2023 Registrations are now LIVE!

Unity 2018.3.0b1 returns exit code 0 even though project is not compiling

Discussion in '2018.3 Beta' started by Clay_More, Sep 21, 2018.

  1. Clay_More

    Clay_More

    Joined:
    Dec 17, 2015
    Posts:
    11
    After upgrading project to version 2018.3.0b1, our automatic-integration server stopped working. After short investigation I've noticed that runinng unity from command line results with exit code 0 even though project has compilation errors. Did someone else also encountered this problem?
     
    Clay_More, Sep 21, 2018
    #1

  2. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,419
    Peter77, Sep 21, 2018
    #2

  3. Clay_More

    Clay_More

    Joined:
    Dec 17, 2015
    Posts:
    11
    @Peter77 It is not issue with Building application, but with tests in editor only (running unity from command line with -runEditorTests argument). So far unity exited with fail code whenever any compilation error in project was found. After update to new version of unity, it's not the case.
     
    Clay_More, Sep 21, 2018
    #3