Issues

Four of five mutation legs test zero mutants: the unmutated tree exceeds the per-crate timeout

bug

#451

· FerroxLabs opened

on Sep 4, 2026

·

0.13.14

[mutants-nightly] wcore-cron — surviving mutants (2026-09-04)

mutation-testing

test-debt

wcore-cron

#449

· github-actions opened

on Sep 4, 2026

·

0.13.14

The #338 c2 Windows residual pin reports the escape CLOSED while the same report shows it open — the probe depends on the parent owning the user's console

#434

· FerroxLabs opened

on Sep 3, 2026

·

0.13.14

mutants-nightly has produced zero data in 87 runs: every leg dies in ~30s on a missing target/ parent, and the step exits 0 so it can never go red

bug

#424

· FerroxLabs opened

on Sep 3, 2026

·

0.13.14

Close the quarantine console bypass with a restricting-SID token, without removing the feature (from #389 c1)

bug

#415

· FerroxLabs opened

on Aug 31, 2026

·

0.13.14

The DENY_CACHE_MAX_DIRS branch of deny_cache is ungraded and needs 100,001 directories to reach (split from #398 c5)

bug

#413

· FerroxLabs opened

on Aug 31, 2026

·

0.13.14

A planning-only lane push buys a full cold hosted Windows compile+test it cannot use

enhancement

#411

· FerroxLabs opened

on Aug 31, 2026

·

0.13.13

[Maintainer] AppContainer categorical-deny disposition: Q-368-honesty forbids the fix while a required soak job tests for it (core#368 c1-c5)

#410

· FerroxLabs opened

on Aug 31, 2026

·

0.13.12

A ci-linux cancellation at the 120-minute budget destroys the JUnit evidence the run already produced

#404

· FerroxLabs opened

on Aug 30, 2026

·

0.13.14

The workspace --lib suite is not ten-times-clean: an ephemeral-port race and three single-sample wall-clock ratios (core#373 c5 remainder)

#403

· FerroxLabs opened

on Aug 30, 2026

·

0.13.14

an_unknown_window_sizes_the_skill_listing precondition cannot pass in a clean container, so every integ/f13 CI run is red

#401

· FerroxLabs opened

on Aug 30, 2026

·

0.13.14

[Maintainer] Decide the permanent disposition of the WhatsApp BRIDGE chunk width (core#360 c1)

#392

· FerroxLabs opened

on Aug 30, 2026

·

0.13.12

Navigation Menu

All issues

Four of five mutation legs test zero mutants: the unmutated tree exceeds the per-crate timeout

[mutants-nightly] wcore-cron — surviving mutants (2026-09-04)

The #338 c2 Windows residual pin reports the escape CLOSED while the same report shows it open — the probe depends on the parent owning the user's console

mutants-nightly has produced zero data in 87 runs: every leg dies in ~30s on a missing target/ parent, and the step exits 0 so it can never go red

Close the quarantine console bypass with a restricting-SID token, without removing the feature (from #389 c1)

The DENY_CACHE_MAX_DIRS branch of deny_cache is ungraded and needs 100,001 directories to reach (split from #398 c5)

A planning-only lane push buys a full cold hosted Windows compile+test it cannot use

[Maintainer] AppContainer categorical-deny disposition: Q-368-honesty forbids the fix while a required soak job tests for it (core#368 c1-c5)

A ci-linux cancellation at the 120-minute budget destroys the JUnit evidence the run already produced

The workspace --lib suite is not ten-times-clean: an ephemeral-port race and three single-sample wall-clock ratios (core#373 c5 remainder)

an_unknown_window_sizes_the_skill_listing precondition cannot pass in a clean container, so every integ/f13 CI run is red

[Maintainer] Decide the permanent disposition of the WhatsApp BRIDGE chunk width (core#360 c1)

Search results