Skip to content

T15633b is fragile on Windows

In !1130 (closed) I saw one build where T15633b failed segfaulted on Windows:

Wrong exit code for T15633b(ghci)(expected 0 , actual 11 )
Stdout ( T15633b ):
True
Stderr ( T15633b ):
TcPluginGHCi

Access violation in generated code when reading 0xfffffffffffffff8

 Attempting to reconstruct a stack trace...

   Frame	Code address
 * 0x54ffaf0	0x3001263 C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2c01263
 * 0x54ffb70	0x2fd578c C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2bd578c
 * 0x54ffbe0	0x2fcacbf C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2bcacbf
 * 0x54ffd30	0x2fcb63f C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2bcb63f
 * 0x54ffe20	0x2fc0270 C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2bc0270
 * 0x54ffed0	0x2fc11c7 C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2bc11c7
 * 0x54fff10	0x2fc1a4f C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2bc1a4f
 * 0x54fff50	0x2fe92f8 C:\GitLabRunner\builds\e963ee11\0\ghc\ghc\inplace\bin\ghc-stage2.exe+0x2be92f8
 * 0x54fff80	0x7ffef5d284d4 C:\Windows\System32\KERNEL32.DLL+0x84d4
 * 0x54fffd0	0x7ffef86be851 C:\Windows\SYSTEM32\ntdll.dll+0x6e851
*** unexpected failure for T15633b(ghci)

I suspect this means that either plugins or GHCi (or the combination of the two) are fragile on Windows. I'm going to mark both T15633b and T15633a as fragile on Windows.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information