Skip to content

Read test-xvfb-paths from ancestor info.rkt files - #24

Merged
samth merged 1 commit into
racket:masterfrom
samth:xvfb-ancestor-info
Oct 19, 2026
Merged

samth merged 1 commit into
racket:masterfrom
samth:xvfb-ancestor-info

Conversation

@samth

@samth samth commented Oct 19, 2026

Copy link
Copy Markdown
Member

path-needs-xvfb? read only the info.rkt in a test's own directory, so a
test listed by an ancestor's info.rkt ran under xvfb-run only if DrDr
had already read that info.rkt. DrDr visits a directory's tests
subdirectory first, so the BC run of gui-test's
framework/tests/group-test.rkt always used the shared display. Like
raco test does for test-omit-paths, path-needs-xvfb? now reads every
info.rkt from the test's directory up to the trunk.

@samth
samth force-pushed the xvfb-ancestor-info branch from 698718f to 64db81a Compare October 19, 2026 14:35
path-needs-xvfb? read only the info.rkt in a test's own directory, so a
test listed by an ancestor's info.rkt ran under xvfb-run only if DrDr
had already read that info.rkt. DrDr visits a directory's tests
subdirectory first, so the BC run of gui-test's
framework/tests/group-test.rkt always used the shared display. Like
raco test does for test-omit-paths, path-needs-xvfb? now reads every
info.rkt from the test's directory up to the trunk.
@samth
samth force-pushed the xvfb-ancestor-info branch from 64db81a to 392b81a Compare October 19, 2026 14:47
@samth
samth merged commit 942aaf5 into racket:master Oct 19, 2026
1 check passed
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.

1 participant