dotnet / dotnet/performance

BDN: Failed to build in Parallel, switching to sequential build

Open
#1,856 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
F#
Stars
773
Forks
301
Avg merge
6d 9h
Merged PRs (30d)
15

Description

I fairly frequently see the message "Failed to build in Parallel, switching to sequential build":
```
C:\gh\performance\src\benchmarks\micro>dotnet run -c Release -f net6.0 -- --filter *BenchI.Array2* *Bytemark.BenchLUDecomp* --coreRun C:\gh\runtime2\artifacts\tests\coreclr\windows.x64.Release\Tests\Core_Root\CoreRun.exe C:\gh\runtime\artifacts\tests\coreclr\windows.x64.Release\Tests\Core_Root\CoreRun.exe -e GitHub
// Validating benchmarks:
// ***** BenchmarkRunner: Start *****
// ***** Found 4 benchmark(s) in total *****
// ***** Building 2 exe(s) in Parallel: Start *****
// ***** Done, took 00:00:39 (39.27 sec) *****
// ***** Failed to build in Parallel, switching to sequential build *****
// ***** Done, took 00:00:59 (59.6 sec) *****
```

It seems surprising this first part of the process takes so much time, but it seems like whatever it's trying to do in parallel isn't working, and ends up wasting a bunch of time.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.