lix/tests
eldritch horrors c39150e6bb diagnose "unexpected EOF" at EOF
this needs a string comparison because there seems to be no other way to
get that information out of bison. usually the location info is going to
be correct (pointing at a bad token), but since EOF isn't a token as
such it'll be wrong in that this case.

this hasn't shown up much so far because a single line ending *is* a
token, so any file formatted in the usual manner (ie, ending in a line
ending) would have its EOF position reported correctly.

(cherry picked from commit 855fd5a1bb781e4f722c1d757ba43e866d370132)
Change-Id: I120c56a962f4286b1ae3b71da7b71ce8ec3e0535
2024-03-18 16:12:46 +01:00
..
functional diagnose "unexpected EOF" at EOF 2024-03-18 16:12:46 +01:00
installer test: Make the installer work on old rhel versions 2023-03-31 15:29:50 +02:00
nixos make the multi-node vm tests a bit more reliable 2024-03-10 10:10:52 +01:00
unit builtins.nixVersion: return fixed fake version 2024-03-17 00:32:19 -07:00