Search Issue Tracker
Fixed in 2018.4.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.8f1
Issue ID
1188715
Regression
No
Unity test running in batch mode fails when adding new assemblies
How to reproduce:
1. Extract the "repro.zip" folder
2. Change path variables according to your machine in "repro.sh" script
3. Execute the "repro.sh" script
Actual result: Unity loses reference to Assembly2.dll and tests fails with compilation errors.
Expected result: Unity keeps the reference and tests are executed.
Reproducible with: 2017.4.33f1, 2018.4.11f1, 2019.1.0a1.
Not reproducible with: 2019.1.0a2, 2019.1.14f1, 2019.2.8f1, 2019.3.0b6, 2020.1.0a8.
Notes:
- With 2017.4.33f1, on the first run the assembly is still missing but the tests are executed.
---------------------------
Fixed in 2019.1.0a2, 2018.4.13f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Add comment