-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SignTool can fail if it repacks too much big stuff at once #13799
Comments
There is one potential issue, and another potential fix:
|
Closed as fixed by serialization of large containers |
We may be experiencing this issue again in the following builds: https://dev.azure.com/dnceng/internal/_build/results?buildId=2394040&view=results edit: ignore, we think this was resolved by dotnet/roslyn#72322 |
Hmm, might want to check the logs and see what parallelism is getting passed to the task. |
Great, let me know if you see it again after the change. |
The change has been merged but the OOM ocurred again: Also other signing errors ocurred, not sure if related: |
I think the other errors are unrelated. It looks like a network error I haven't seen before, on the Microbuild side. I suggest setting SignToolRepackMaximumParallelFileSize to 64 and see whether that helps things. The problem with roslyn is that it has 3 copies of basically every file, and a lot of files in the mid-range size. |
@dibarbet, when adding a new nupkg to the roslyn build, started hitting OOMs on the repack steps. Upon further investigation, it seems likely that the repack step, which runs in parallel, is OOMing when there are too many large packages in memory at once. I think we have not hit this in the past because most repos have only a few large unpkgs or zip files, thus it is unlikely that their streams will be open at the same time.
Release Note Category
Release Note Description
The text was updated successfully, but these errors were encountered: