Log delivery and file sink tests
Section titled “Log delivery and file sink tests”Inno.Core.Logging.Tests verifies the Logging contracts through their public entry points. Use this page to locate relevant assertions; it is not a report that these tests passed for your current change.
Behavior covered
Section titled “Behavior covered”The suite tests nested entries in queue order without recursive delivery, flush waiting for in-flight receive, serialized sink access under concurrent producers, and quarantine of a failing sink. File tests preserve complete oversized entries, distinct sink-owned files, completed-write visibility and rotation byte limits. Compiler categories remain independent of runtime path separators.
Environment and execution
Section titled “Environment and execution”The project declares the domain validation layer. Use the shared validation workflow to select its actual dependencies and environment. Inspect the pinned project file for package and project references.
A focused diagnostic from the engine root is:
dotnet test tests/core/Inno.Core.Logging.Tests/Inno.Core.Logging.Tests.csproj --configuration Debug --disable-build-servers -m:1 -nodeReuse:falseUse --filter FullyQualifiedName~MethodName to investigate one case. A filtered run does not replace the obligations in the validation plan. Restore the declared SDK, packages and any tool/process prerequisites before executing; preserve cancellation, thread and cleanup requirements.
Scenario reference
Section titled “Scenario reference”These representative methods are preserved from the original reference and checked against the pinned source. The linked files contain all assertions and parameterized cases.
File Log Sink
Section titled “File Log Sink”Read the assertions. Representative entry points:
RouterFlushMakesCompletedFileWritesObservableRapidRotationRetainsTheCurrentEntryAndHonorsTheByteLimitOversizedEntriesRemainCompleteAndRotateBeforeTheNextEntryMultipleSinksOwnDistinctFilesInTheSameDirectory
Inline Log Delivery
Section titled “Inline Log Delivery”Read the assertions. Representative entry points:
NestedEntriesReachEverySinkInQueueOrderLongNestedChainsDoNotReenterDeliveryFlushWaitsForAnEntryAlreadyInsideReceiveConcurrentProducersNeverInvokeASinkConcurrently
Logging Behavior
Section titled “Logging Behavior”Read the assertions. Representative entry points:
InlineDeliveryIsImmediateAndQuarantinesAFailingSinkUnknownDeliveryPoliciesFailAtConstructionCompilerSourceCategoriesAreIndependentOfRuntimePathSeparatorsBrokenFailureReportingCannotStopHealthySinkDelivery
Extend safely
Section titled “Extend safely”Follow the shared suite-maintenance guidance. Preserve this suite’s owner-thread, resource-release and failure assertions when adding cases.