ci: proptest nightly

[federico-stacks]

Description

This PR add proptest worflow that run all the proptests in the code base using an elevated case count.
In case of test execution failure:

• the workflow saves the test regressions files as artifact and take them into account in a next run.
• send a slack notification to the github-ci-nightly channel (a notification is also sent for unexpected worflow error)

This workflow add also support for proptest tests written with madhouse-rs setting the env variable MADHOUSE=1

Applicable issues

• fixes [CI] implement proptest nightly automation #7004

Additional info (benefits, drawbacks, caveats)

Checklist

• Test coverage for new or modified code paths
• For new Clarity features or consensus changes, add property tests (see docs/property-testing.md)
• Changelog is updated
• Required documentation changes (e.g., rpc/openapi.yaml for RPC endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo

[BowTiedRadone]

@federico-stacks It'd be a great idea to also run https://github.com/stacks-network/madhouse-rs tests as part of this nightly workflow. For example, #6912 adds some madhouse-rs scenario tests. We can pick a naming convention (e.g. prop_scenario_) and I can update them so they get picked up.

[federico-stacks]

@federico-stacks It'd be a great idea to also run https://github.com/stacks-network/madhouse-rs tests as part of this nightly workflow. For example, #6912 adds some madhouse-rs scenario tests. We can pick a naming convention (e.g. prop_scenario_) and I can update them so they get picked up.

Actually if they are normal #[test] (as it seems to be), you can tag them with #[tag(t_prop)] (as described in the doc: https://github.com/stacks-network/stacks-core/blob/develop/docs/property-testing.md), and they would be gathered automatically.

[federico-stacks]

@BowTiedRadone one more reasoning about the madhause-rs tests. would yhey be still dependent from PROPTEST_CASES env variable? Just wanted to undertand if we can threat them as "native" proptest tests, or if we could need a dedicated process.

[BowTiedRadone]

@federico-stacks They depend on both PROPTEST_CASES and MADHOUSE env vars.

A madhouse-rs test should ideally run in two modes:

• Without MADHOUSE=1: runs the commands in the scenario as-is with randomly generated arguments.
• With MADHOUSE=1: treats the listed commands as a selection pool and generates randomized sequences from them alongside random arguments.

By default, madhouse-rs runs one proptest case. Setting MADHOUSE=1 alongside PROPTEST_CASES=N will produce N randomized sequences from the listed commands.

[federico-stacks]

@federico-stacks They depend on both PROPTEST_CASES and MADHOUSE env vars.

A madhouse-rs test should ideally run in two modes:

• Without MADHOUSE=1: runs the commands in the scenario as-is with randomly generated arguments.
• With MADHOUSE=1: treats the listed commands as a selection pool and generates randomized sequences from them alongside random arguments.

By default, madhouse-rs runs one proptest case. Setting MADHOUSE=1 alongside PROPTEST_CASES=N will produce N randomized sequences from the listed commands.

@BowTiedRadone So, if we want to run them in this workflow, we also need to set MADHOUSE=1 env variable, if I understand correctly.

[BowTiedRadone]

@federico-stacks Exactly. That's correct and I believe should be the only addition.

[coveralls]

Coverage Report for CI Build 24389109761

Coverage decreased (-0.03%) to 85.685%

Details

• Coverage decreased (-0.03%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 1819 coverage regressions across 61 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

1819 previously-covered lines in 61 files lost coverage.

Top 10 Files by Coverage Loss	Lines Losing Coverage	Coverage
stackslib/src/net/inv/epoch2x.rs	222	79.44%
stackslib/src/net/chat.rs	200	92.93%
stacks-node/src/nakamoto_node/miner.rs	134	87.08%
stackslib/src/net/api/postblock_proposal.rs	107	82.16%
stackslib/src/clarity_vm/database/marf.rs	99	60.67%
clarity/src/vm/contexts.rs	75	92.36%
clarity/src/vm/functions/database.rs	75	92.36%
stackslib/src/net/codec.rs	69	91.63%
stackslib/src/net/p2p.rs	69	74.04%
stackslib/src/clarity_vm/database/ephemeral.rs	61	56.82%

---

Coverage Stats

Relevant Lines:	217886
Covered Lines:	186696
Line Coverage:	85.69%
Coverage Strength:	17128954.37 hits per line

---

💛 - Coveralls

[radu-stacks]

Looking good! Left only a few suggestions and nits.

[radu-stacks]

Only 2 comments left from my side:

[wileyj]

lgtm

[radu-stacks]

LGTM