Skip to content

Commit e014ab9

Browse files
committed
Record that eval had never worked on 26, and why nothing noticed
CI's e2e job pins Java 21, so the suite has never run against a 26 branch -- which is a bigger hole than the Groovy bug it was hiding.
1 parent 264759e commit e014ab9

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

docs/ROADMAP.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -501,6 +501,17 @@ broke, reaches the client a few ticks later, and lands a block or two from where
501501
so `drops` is read ten ticks after the break and carries each item's position. Without the position
502502
there is nowhere to walk to.
503503

504+
**`eval` had been dead on Minecraft 26 all along.** Running the suite on the 26 worktree by hand --
505+
which the new mining phases made worth doing -- failed on an `eval` assertion with
506+
`Unsupported class file major version 69`: the init script pinned Groovy 4.0.22, which cannot read
507+
Java 25 class files. So `eval` and `wait --expr`, a headline feature, had never worked on either 26
508+
branch. Nothing caught it because CI's e2e job pins Java 21 and never gets far enough there to try.
509+
Groovy 5.1.1 fixes it and passes on 1.21 too.
510+
511+
**A CI gap worth closing separately:** the e2e job's `java-version: 21` means the suite has never
512+
run against a 26 branch at all. That is why a whole feature could be broken there unnoticed, and it
513+
is a bigger hole than any single bug it has been hiding.
514+
504515
**`give` does not put the item in your hand.** It finds a free slot and leaves the selection alone,
505516
so the e2e mined cobblestone bare-handed: 202 ticks, and no drop, because cobblestone needs a
506517
pickaxe. That is the tick count doing exactly the job it was added for — it is now asserted from

0 commit comments

Comments
 (0)