Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.3.4f1
2023.1.2f1
2023.2.0a21
2023.3.0a3
Issue ID
UUM-41177
Regression
Yes
Build re-using previous Bee Graph pollutes logs with unwanted error lines when files are changed by source control.
Reproduction steps:
1. Create a repository from the attached project “BuildBee” via a source control application
2. In the source control application checkout the “init commit” commit
3. Open the project in the Editor
4. Build the Player ( File > Build Settings, then in Build Settings window select Build)
5. Close the Editor
6. In the source control application, checkout the “config 2” commit
7. Repeat steps 3 and 4
8. Observe the “Editor.log” file (default location for Win10: “C:\Users\{username}\AppData\Local\Unity\Editor”)
Expected result: There are no “could not be found” errors for files that were removed via source control
Actual result: “error CS2001: Source file 'D:\Unity cases\Rsp\Assets/WidgetY.cs' could not be found.” error appears
Reproducible with: 2022.2.0a12, 2022.3.4f1, 2023.1.2f1, 2023.2.0a21
Not reproducible with: 2021.3.27f1, 2022.2.0a11
Reproducible on: Windows 10
Note: The application “Fork” was used for the reproduction steps
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
- [Editor] Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
Resolution Note:
We dont have a great solution for not writing out the errors in the log.
The first run is an optimistic run, where we try to build reusing the same build graph as before. If it fails or we find that the graph is outdated, we will rerun.
Filtering out the logs are not something we can do without bigger changes.
As we are working on a new compilation pipeline, we will focus on fixing it there.
Resolution Note (2023.3.X):
We dont have a great solution for not writing out the errors in the log.
The first run is an optimistic run, where we try to build reusing the same build graph as before. If it fails or we find that the graph is outdated, we will rerun.
Filtering out the logs are not something we can do without bigger changes.
As we are working on a new compilation pipeline, we will focus on fixing it there.