[CI] LibTTYTest.test2 fails sometimes on Linux

[MarcusDenker]

We are seeing random failures of LibTTYTest.test2 on linux:

Error Message

Got 'Error in tty_spawn at execve(path, argv, envp): Aucun fichier ou dossier de ce type ' instead of 'Error in tty_spawn at execve(path, argv, envp): No such file or directory '.
Stacktrace

TestFailure
Got 'Error in tty_spawn at execve(path, argv, envp): Aucun fichier ou dossier de ce type
' instead of 'Error in tty_spawn at execve(path, argv, envp): No such file or directory
'.
LibTTYTest(TestAsserter)>>assert:description:resumable:
LibTTYTest(TestAsserter)>>assert:description:
LibTTYTest(TestAsserter)>>assert:equals:
LibTTYTest>>assertProcessSpawnedWithFileDescriptor:path:arguments:environment:input:writes:hasStatus:
LibTTYTest>>assertProcessSpawnedWithPseudoTerminalPath:arguments:environment:input:writes:hasStatus:
LibTTYTest>>test2
LibTTYTest(TestCase)>>performTest
LibTTYTest>>performTest

Example for a testrun with the failure: #17126

[Rinzwind]

It specifically seems to fail when the tests run on ‘gilda’, see the pages opened by the snippet given below (based on a similar one I gave in issue #15105). Presumably it runs the tests with the relevant internationalization environment variable set to French. I’ve opened a pull request to modify the test to take that into account: pull request #17138.

{ { 17135. 1 to: 2 }. { 17134. 1 to: 1 }. { 17133. 1 to: 1 }. { 17132. 1 to: 1 } }
	do: [ :arguments |
		arguments bind: [ :pullRequestNumber :buildNumbers |
			buildNumbers do: [ :buildNumber |
				{ 'testReport/Unix64.UnifiedFFI.Tests/LibTTYTest/unix_64___Tests_unix_64___test2/'.
					'execution/node/49/log/' } do: [ :suffix |
					WebBrowser openOn: ('https://ci.inria.fr/pharo-ci-jenkins2/job' ,
						'/Test%20pending%20pull%20request%20and%20branch%20Pipeline' ,
						'/view/change-requests/job/PR-{1}/{2}/{3}'
							format: { pullRequestNumber. buildNumber. suffix }) ] ] ] ]

[Rinzwind]

@MarcusDenker: Can someone take a look at adding English to the locales on ‘gilda’ (see pull request #17138 for details) ?

[MarcusDenker]

this is now fixed