Skip to content

test: capture incremental recursive warning loss#12

Closed
teerthsharma wants to merge 1 commit into
kinto0:export-D112591162from
teerthsharma:test-incremental-recursive-warning-loss
Closed

test: capture incremental recursive warning loss#12
teerthsharma wants to merge 1 commit into
kinto0:export-D112591162from
teerthsharma:test-incremental-recursive-warning-loss

Conversation

@teerthsharma

Copy link
Copy Markdown

Summary

Adds a deterministic regression test for facebook#4216.

A comment-only edit to one member of a recursive two-module binding cycle loses the non-convergent-recursion warning during an incremental recheck, while a fresh check of the byte-identical final sources emits it.

This is a test-only stack on facebook#4188. It targets that PR's head because current main reaches the older capped-propagation failure before this behavior is exposed.

Test shape

  • Fixes the worker count at one to remove scheduler variability.
  • Asserts the cold result contains non-convergent-recursion.
  • Asserts warm and cold diagnostics match.
  • Uses #[should_panic] so the regression stays green until the production fix lands.

No production code, dependencies, or documentation are changed.

Verification

  • Red phase: the unwrapped test failed with warm [] versus cold ["non-convergent-recursion"].
  • Expected-panic phase: cargo test -p pyrefly test_incremental_recursive_warning_survives_comment_edit -- --nocapture
  • Formatting/lint: python3 test.py --no-test --no-tensor-shapes --no-conformance --no-jsonschema
  • git diff --check

Signed-off-by: teerth sharma <teerths57@gmail.com>
@kinto0 kinto0 closed this Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants