Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

ystem.InvalidOperationException: File access reported from process

未关闭
#159 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
csharp

调研方向

从链接的 Azure 构建日志开始,然后通过 Common/FileAccess/FileAccessRepository.cs 第 215 行以及 Common/MSBuildCachePluginBase.cs 第 491 行和第 511 行追踪失败原因。确认延迟的文件访问报告是如何生成的,并确定此情况下的预期行为;完成内容应包括可复现的诊断,以及一项回归检查,证明构建不再意外失败。

由索引模型根据 Issue 内容生成。

描述

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1523806&view=logs&j=1f132584-ab08-5fbf-e5d0-5685de454342&t=7bc96f1d-1be1-57c3-f7fb-1c61e7f4a005

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()
主要语言
C#
星标
64
派生
24
平均合并
1 天 14 小时
30 天内合并 PR
2

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/MSBuildCache 的其他 Issue

查看 microsoft/MSBuildCache 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。