Skip to content

ci(coyote): update comments for fuzzing-mode TestKit concurrency tests #701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Chris-Wolfgang merged 3 commits into from
Oct 12, 2026
Merged

ci(coyote): update comments for fuzzing-mode TestKit concurrency tests #701

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f15192d
ci(coyote): update comments for fuzzing-mode TestKit concurrency tests
Chris-Wolfgang Oct 5, 2026
d3be7d7
Merge branch 'main' into ci/coyote-comments-fuzzing-mode
Chris-Wolfgang Oct 12, 2026
04d8e68
Merge branch 'main' into ci/coyote-comments-fuzzing-mode
Chris-Wolfgang Oct 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions .github/workflows/coyote.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,10 @@ name: Concurrency (Coyote)
# - schedule (weekly) + workflow_dispatch — the deep run (10000 iterations/test).
#
# The TestKit doubles have their own systematic scenarios (tests/Wolfgang.Etl.TestKit.Tests
# .Concurrency, #126): xunit-hosted Coyote TestingEngine runs that only execute when the
# assembly was rewritten and COYOTE_REWRITTEN=1 is set (#365). That project targets net10.0;
# .Concurrency, #126): xunit-hosted Coyote TestingEngine runs. They always run: the ordinary
# test sweep runs them un-rewritten in systematic fuzzing mode (timing perturbation, no
# controlled schedule), and this workflow rewrites the assembly and sets COYOTE_REWRITTEN=1
# so the same tests run under controlled scheduling (#365). That project targets net10.0;
# `coyote rewrite` only patches the IL, so the runtime gap above does not apply.
#
# NOT implemented: the optional 24h soak (handle/thread/memory-leak hunting via
Expand Down Expand Up @@ -132,9 +134,9 @@ jobs:
run: coyote rewrite rewrite.coyote.json

- name: Run the systematic tests under the rewritten assemblies
# RunSystematic early-returns without this flag (the normal PR sweep must not
# run un-rewritten Coyote, which reports false deadlocks); with it, each [Fact]
# drives a TestingEngine over 500 controlled interleavings and fails on any bug.
# Without this flag RunSystematic uses systematic fuzzing mode (what the ordinary
# test sweep runs, since un-rewritten Coyote cannot control the schedule); with it,
# each [Fact] drives a TestingEngine under controlled scheduling and fails on any bug.
env:
COYOTE_REWRITTEN: '1'
run: dotnet test "$PROJECT/Wolfgang.Etl.TestKit.Tests.Concurrency.csproj" -c Release --no-build --logger "console;verbosity=normal"
Loading