Skip to content

Refactoring core routing and improving stability #323

Refactoring core routing and improving stability

Refactoring core routing and improving stability #323

Re-run triggered January 13, 2025 14:41
Status Failure
Total duration 4m 11s
Artifacts 1

dotnet-test.yml

on: pull_request
Build and Run Unit tests
4m 1s
Build and Run Unit tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
Build and Run Unit tests
Process completed with exit code 1.
Build and Run Unit tests
This action finished successfully, but test results have status failure.
SnapshotImport_AndThenRegularImportTest (MeshWeaver.Import.Test.SnapshotImportTest) failed: MeshWeaver.Import.Test.SnapshotImportTest#L0
test/MeshWeaver.Import.Test/TestResults/_fv-az1335-272_2025-01-13_14_44_49.trx [took 0s]
Build and Run Unit tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and Run Unit tests: src/MeshWeaver.Messaging.Hub/MessageHub.cs#L562
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Build and Run Unit tests: src/MeshWeaver.Messaging.Hub/MessageHub.cs#L562
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Build and Run Unit tests: src/MeshWeaver.Messaging.Hub/MessageHub.cs#L562
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
Build and Run Unit tests: src/MeshWeaver.Messaging.Hub/MessageHub.cs#L562
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.

Artifacts

Produced during runtime
Name Size
testResults Expired
89.9 KB