Skip to content

test: replace flaky large file URLs with local fixture - #2294

Merged
mre merged 1 commit into
masterfrom
fix/local-large-file-test
Sep 20, 2026
Merged

mre merged 1 commit into
masterfrom
fix/local-large-file-test

Conversation

@mre

@mre mre commented Sep 6, 2026 •

Copy link
Copy Markdown
Member

Replace the large-file CLI test's proof.ovh.net dependency with a local streaming HTTP fixture. This preserves the lazy-download and fragment coverage without relying on a rate-limited third-party host.

See the discussion over at #2293.

@mre
mre force-pushed the fix/local-large-file-test branch from 941dec0 to ddee082 Compare September 6, 2026 15:56
@mre
mre force-pushed the fix/local-large-file-test branch from ddee082 to 3e7c554 Compare September 6, 2026 16:02
@mre

mre commented Sep 6, 2026

Copy link
Copy Markdown
Member Author

I decided to remove the /fragment endpoint again. Fragment behavior is already covered by dedicated tests, so this now keeps only the small raw TCP fixture needed to model an incomplete 10 GB response. wiremock buffers response bodies and delays before sending headers, which cannot represent this case. The listener handles two connections because the test invokes lychee twice against the same URL: once with --include-fragments and no fragment, and once with a fragment but without --include-fragments.

@mre
mre merged commit fd3f35b into master Sep 20, 2026
8 checks passed
@mre
mre deleted the fix/local-large-file-test branch September 20, 2026 15:45
@mre mre mentioned this pull request Sep 20, 2026
@thomas-zahner

Copy link
Copy Markdown
Member

That's a great alternative, thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants