Search Issue Tracker
Fixed in 2017.2.0f3
Votes
6
Found in
5.6.1f1
Issue ID
912728
Regression
No
ENABLE_PLAYMODE_TESTS_RUNNER define is true even when PlayMode tests are disabled
To reproduce:
1. Download and open attached "repro912728.zip" project.
2. Go to build settings.
3. Build the project on any platform.
Expected result: Project successfully builds even when PlayMode tests are disabled.
Actual result: Project fails to build with PlayMode tests disabled and errors appear in the console.
Reproduced with: 2017.2.0a1, 2017.1.0b7, 5.6.1p2, 5.5.4f1.
Notes: Could not test on earlier versions because PlayMode tests were not yet implemented. ENABLE_PLAYMODE_TESTS_RUNNER is always set in script, no matter if user has enabled Play mode tests or not.
___________________________________
Fixed now that we support assembly definition files since Unity 2017.2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
KK-Kon
Jul 29, 2018 02:18
sorry, never mind.
KK-Kon
Jul 28, 2018 17:52
please back port to 5.6