microsoft / microsoft/MSBuildCache
ystem.InvalidOperationException: File access reported from process
Offen
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- C#
- Sterne
- 64
- Forks
- 24
- Ø Merge
- 1 T. 14 Std.
- Gemergte PRs (30 T.)
- 2
Beschreibung
MSBUILD : warning : HandleFileAccess failed after 0 ms: System.InvalidOperationException: File access reported from process `ProcessId: 2192` after the project finished. This may lead to incorrect caching. Node Id: SRC_ADAPTER_MSTESTADAPTER.PLATFORMSERVICES_MSTESTADAPTER.PLATFORMSERVICES.CSPROJ_OKU0DL90CASQU8S9EBLOAA, Path: C:\Windows\System32\ci.dll
MSBUILD : warning : at Microsoft.MSBuildCache.FileAccess.FileAccessRepository.FileAccessesState.AddFileAccess(FileAccessData fileAccessData) in D:\a\_work\1\s\src\Common\FileAccess\FileAccessRepository.cs:line 215
MSBUILD : warning : at Microsoft.MSBuildCache.MSBuildCachePluginBase`1.HandleFileAccessInner(FileAccessContext fileAccessContext, FileAccessData fileAccessData) in D:\a\_work\1\s\src\Common\MSBuildCachePluginBase.cs:line 511
MSBUILD : warning : at Microsoft.MSBuildCache.MSBuildCachePluginBase`1.<>c__DisplayClass62_0.<HandleFileAccess>b__0() in D:\a\_work\1\s\src\Common\MSBuildCachePluginBase.cs:line 491
MSBUILD : warning : at Microsoft.MSBuildCache.MSBuildCachePluginBase`1.TimeAndLog(PluginLoggerBase logger, Action inner, String memberName) in D:\a\_work\1\s\src\Common\MSBuildCachePluginBase.cs:line 1329
Unhandled Exception: System.InvalidOperationException: File access reported from process `ProcessId: 2192` after the project finished. This may lead to incorrect caching. Node Id: SRC_ADAPTER_MSTESTADAPTER.PLATFORMSERVICES_MSTESTADAPTER.PLATFORMSERVICES.CSPROJ_OKU0DL90CASQU8S9EBLOAA, Path: C:\Windows\System32\ci.dll
at Microsoft.MSBuildCache.FileAccess.FileAccessRepository.FileAccessesState.AddFileAccess(FileAccessData fileAccessData) in D:\a\_work\1\s\src\Common\FileAccess\FileAccessRepository.cs:line 215
at Microsoft.MSBuildCache.MSBuildCachePluginBase`1.HandleFileAccessInner(FileAccessContext fileAccessContext, FileAccessData fileAccessData) in D:\a\_work\1\s\src\Common\MSBuildCachePluginBase.cs:line 511
at Microsoft.MSBuildCache.MSBuildCachePluginBase`1.<>c__DisplayClass62_0.<HandleFileAccess>b__0() in D:\a\_work\1\s\src\Common\MSBuildCachePluginBase.cs:line 491
at Microsoft.MSBuildCache.MSBuildCachePluginBase`1.TimeAndLog(PluginLoggerBase logger, Action inner, String memberName) in D:\a\_work\1\s\src\Common\MSBuildCachePluginBase.cs:line 1340
at Microsoft.MSBuildCache.MSBuildCachePluginBase`1.HandleFileAccess(FileAccessContext fileAccessContext, FileAccessData fileAccessData) in D:\a\_work\1\s\src\Common\MSBuildCachePluginBase.cs:line 493
at Microsoft.Build.ProjectCache.ProjectCacheService.<>c__DisplayClass19_1.<CreateAndInitializePluginAsync>b__2(BuildRequest buildRequest, FileAccessData fileAccessData)
at Microsoft.Build.FileAccesses.FileAccessManager.ReportFileAccess(FileAccessData fileAccessData, Int32 nodeId)
at Microsoft.Build.BackEnd.DetouredNodeLauncher.DetoursEventListener.HandleFileAccess(FileAccessData fileAccessData)
at BuildXL.Processes.SandboxedProcessReports.FileAccessReportLineReceived[T](T& data, FileAccessReportProvider`1 parser, Boolean isAnAugmentedFileAccess, String& errorMessage) in \.\Public\Src\Engine\Processes\SandboxedProcessReports.cs:line 849
at BuildXL.Processes.SandboxedProcessReports.ReportLineReceived(String data) in \.\Public\Src\Engine\Processes\SandboxedProcessReports.cs:line 378
at BuildXL.Processes.SandboxedProcess.ReportLineReceived(String data) in \.\Public\Src\Engine\Processes\SandboxedProcess.cs:line 555
at BuildXL.Processes.Internal.AsyncPipeReader.FlushMessageQueue() in \.\Public\Src\Engine\Processes\Internal\AsyncPipeReader.cs:line 435
at BuildXL.Processes.Internal.AsyncPipeReader.GetLinesFromCharBuffers(Int32 len) in \.\Public\Src\Engine\Processes\Internal\AsyncPipeReader.cs:line 410
at BuildXL.Processes.Internal.AsyncPipeReader.BuildXL.Native.Streams.IIOCompletionTarget.OnCompletion(FileAsyncIOResult asyncIOResult) in \.\Public\Src\Engine\Processes\Internal\AsyncPipeReader.cs:line 314
at BuildXL.Native.Streams.Windows.IOCompletionManager.<>c.<ReleaseOvelappedAndQueueCompletionNotification>b__18_0(Object state) in \.\Public\Src\Utilities\Native\Streams\Windows\IOCompletionManager.cs:line 255
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit dem verlinkten Azure-Build-Log und verfolge den Fehler anschließend durch Common/FileAccess/FileAccessRepository.cs in Zeile 215 sowie Common/MSBuildCachePluginBase.cs in den Zeilen 491 und 511. Bestätige, wie der verzögerte Dateizugriffsbericht erzeugt wird, und ermittle das erwartete Verhalten für diesen Fall; zum Abschluss sollten eine reproduzierbare Diagnose und eine Regressionprüfung gehören, die zeigt, dass der Build nicht mehr unerwartet fehlschlägt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- csharp
- Bereich
- build-system, tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100