Skip to content
.NET

cached-command should use a backing pool, in particular for async APIs #404

Sign in to view logs

cached-command should use a backing pool, in particular for async APIs

cached-command should use a backing pool, in particular for async APIs #404

Triggered via pull request March 27, 2025 16:12
@mgravellmgravell
opened #150
cache-store
Status Failure
Total duration 4m 14s
Artifacts –

dotnet.yml

on: pull_request
build
4m 7s
build
Fit to window
Zoom out
Zoom in

Annotations

1 error
build
Process completed with exit code 1.