dotnet / dotnet/performance

[wasm] Cirtuclar Dependency Error running benchmarks using wasm with out a custom runtime pack

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

Description

Repo:

$MYDOTNET here points at a dotnet host using net5.0:

```
> $MYDOTNET run -c Release --framework netcoreapp5.0 MicroBenchmarks.csproj --filter "*Burgers*" --cli $MYDOTNET --runtimes wasm --wasmMainJS $HOME/workspace/runtime-wasm-test-build//src/mono/wasm/runtime-test.js
```

THe harness will run, but individual benchmarks will fail with this error:

```
/Users/naricc/workspace/performance-fan-repro/artifacts/bin/MicroBenchmarks/Release/netcoreapp5.0/d94a3150-1519-452d-9b76-f8309de68843/BenchmarkDotNet.Autogenerated.csproj(27,11): error MSB4006: There is a circular dependency in the target dependency graph involving target "Publish".
Build FAILED.
```

This error doesn't occur if a custom runtime pack is specified with --customRuntimePack (probably the most common use case for wasm).

I'm not sure if this is a problem for dotnet/runtime or dotnet/performance, but I am putting it here for now. It may have something to do with a change in how wasm apps are constructed.

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.