test(ci): fail when a CI-path extractor stops matching by Chemaclass · Pull Request #1162 · TypedDevs/bashunit

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass · 2026-08-13T18:45:54Z

🤔 Background

Related #1161

The guards collect workflow paths that do not resolve on disk and assert
that set is empty, so an extractor that stops matching finds nothing to check
and the assertion holds. Renaming the test_path: pattern leaves all three
tests green — nothing goes red at all.

This file exists because CI path rot has shipped twice: #960 moving paths, and
coverage.yml globbing in a shell step while its non-blocking nightly run sat
red for days.

💡 Changes

Assert both extractors still find the paths they parse
Floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated — fewer than it looks, because most jobs share the same paths
Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist

The guards collect workflow paths that do not resolve and assert the set is empty, so an extractor that stops matching finds nothing to check and the assertion holds. Renaming the test_path: pattern left all three tests in this file green -- nothing went red at all. This file exists because CI path rot has shipped twice: #960 moving paths, and coverage.yml globbing in a shell step while its non-blocking nightly run sat red for days. Assert both extractors still find what they parse. The floors sit under the current counts: 18 test_path: keys, and 3 distinct tests/ references once the workflows are deduplicated -- fewer than it looks, because most jobs share the same paths. Verified against two mutations: a broken test_path: pattern, and a workflow directory that does not exist. Closes#1161

The new guard failed on Alpine, and the reason is the bug it was written to find: BusyBox grep does not honour --include, so `grep -r ... --include='*.yml'` produced nothing there and 'every tests/ path a workflow names resolves' had been passing on Alpine by having no paths to check. The workflows directory is flat, so an explicit glob is equivalent on GNU grep and works on BusyBox. Verified in an alpine:3 container: 0 paths before, 3 after, matching macOS.

Chemaclass added the bug Something isn't working label Aug 13, 2026

Chemaclass self-assigned this Aug 13, 2026

Chemaclass merged commit 7d4b05e into mainAug 13, 2026
37 checks passed