Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
Issue ID
UUM-82688
Regression
No
[2021.3 only] ExecuteMethod uses cached data when running validations after a CI checkout
Reproduction steps:
1. Connect to the remote PC and open the project folder (see Internal notes)
2. Check if the required files exist and restore them if needed (see Internal notes)
3. Run the “RunTests.bat”, wait for the cmd to close and look at the log.txt file generated from the .bat file
4. Using CTRL+F, search for “BUILD TOOLS: SafeSubmitValidation : Validation successful” to confirm that it was successful
5. Delete the files mentioned in the Internal notes
6. Run the “RunTests.bat”, wait for the cmd to close and look at the log.txt file generated from the .bat file
7. Using CTRL+F, search for “BUILD TOOLS: SafeSubmitValidation : Validation successful”
8. Observe the results
Expected Result: The validation fails
Actual Result: The validation succeeds
Reproducible with: 2021.3.28f1
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Note:
- Running the “RunTests.bat” a second time after deleting the files, the validation fails which is expected behavior
- Deleting the library or just opening the project once after the checkout results in the expected behavior
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
There are no fixes planned for this Bug