Skip to content

Anchor the push-number rewrite to the build directory - #17

Merged
samth merged 1 commit into
racket:masterfrom
samth:anchor-rev-scrub
Sep 23, 2026
Merged

samth merged 1 commit into
racket:masterfrom
samth:anchor-rev-scrub

Conversation

@samth

@samth samth commented Sep 23, 2026

Copy link
Copy Markdown
Member

DrDr scrubs push-specific paths from captured output, so that a log
changes only when the test's behavior does. It replaced the push number
as a bare string, so it also rewrote every other occurrence of those
digits. On push 73506 raco pkg show therefore reported expeditor as
changed, because its checksum ends in that number:

65e20a410bdc5f09c0682a1bb57cac2b68d73506
65e20a410bdc5f09c0682a1bb57cac2b68d

frtime did the same on push 73507, and any push whose number appears in
an installed package's checksum will do it again. Replace the build
directory joined with the push number instead; output for real build
paths does not change.

DrDr scrubs push-specific paths from captured output, so that a log
changes only when the test's behavior does. It replaced the push number
as a bare string, so it also rewrote every other occurrence of those
digits. On push 73506 `raco pkg show` therefore reported expeditor as
changed, because its checksum ends in that number:

  65e20a410bdc5f09c0682a1bb57cac2b68d73506
  65e20a410bdc5f09c0682a1bb57cac2b68d<current-rev>

frtime did the same on push 73507, and any push whose number appears in
an installed package's checksum will do it again. Replace the build
directory joined with the push number instead; output for real build
paths does not change.
@samth
samth merged commit bc14596 into racket:master Sep 23, 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