exa/xtests/outputs/passwd_long_group_header.ansitxt

[4mPermissions[0m [4mSize[0m [4mUser[0m      [4mGroup[0m     [4mDate Modified[0m [4mName[0m
.[1;33mr[31mw[0m[38;5;244m-[33mr[38;5;244m--[33mr[38;5;244m--[0m     [1;32m0[0m cassowary 616       [34m 1 Jan 12:34[0m  unknown-gid
.[1;33mr[31mw[0m[38;5;244m-[33mr[38;5;244m--[33mr[38;5;244m--[0m     [1;32m0[0m 666       cassowary [34m 1 Jan 12:34[0m  unknown-uid
-												Protect xtests against different default users

The Vagrant tests assumed that there’d be a user called “vagrant” that would run the tests and create the files by default. Files would be owned by vagrant:vagrant by default, and this worked, until it came time to change that username. The naïve method was a search-and-replace, but this caused problems when the new user’s name wasn’t exactly the same length as the previous one.

So to fix this, we now have our own user, named after the first animal I thought of, that makes the files’ owners and groups independent of the default user of whichever VM image the xtests are running on.

Another place where it was hard-coded was the home directory, which was “/home/vagrant”, where the awkward testcases live. That last one has been changed to just “/testcases”, which has no mention of the user in it.

											
										
										
											2017-04-28 18:34:23 +00:00
+								[4mPermissions[0m [4mSize[0m [4mUser[0m      [4mGroup[0m     [4mDate Modified[0m [4mName[0m
 								.[1;33mr[31mw[0m[38;5;244m-[33mr[38;5;244m--[33mr[38;5;244m--[0m     [1;32m0[0m cassowary 616       [34m 1 Jan 12:34[0m  unknown-gid
 								.[1;33mr[31mw[0m[38;5;244m-[33mr[38;5;244m--[33mr[38;5;244m--[0m     [1;32m0[0m 666       cassowary [34m 1 Jan 12:34[0m  unknown-uid