-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
sporadic build break due to contention on output of runtime.native.System.IO.Ports #57049
Comments
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Details(using latest runtime-main in runtimelab, which closely matches runtime main) https://dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_apis/build/builds/1282740/logs/50
Usually this means the project is building twice concurrently (ie., with different global properties) Note this is the neutral architecture flavor, ie, there are:
Looking at the log from a successful OSX build, it appears the project is being built twice:
@ericstj any thoughts about where the issue might be? Ill try to get the bin log.
|
@ViktorHofer could it be related to the change of not having pkgproj's anymore? |
It most definitely is related to my change as before those files didn't exist. There's an offline Teams thread about this in which I commented that I will look into the issue. Haven't had time for it yet though. |
The binlog was overwritten by the second attempt :( |
Should be fixed by #57118. The runtime.native.System.IO.Ports.proj project was indeed overbuilding. That said, without a binlog I can't figure out why global properties differed. |
(using latest runtime-main in runtimelab, which closely matches runtime main)
https://dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_apis/build/builds/1282740/logs/50
Usually this means the project is building twice concurrently (ie., with different global properties)
In a working build,
Note this is the neutral architecture flavor, ie, there are:
Looking at the log from a successful OSX build, it appears the project is being built twice:
@ericstj any thoughts about where the issue might be? Ill try to get the bin log.
The text was updated successfully, but these errors were encountered: