Skip to content

T14999 fails with quick build flavour

If I run the T14999 test case using a quick build of GHC, it fails with:

=====> 1 of 1 [0, 0, 0]
Actual stdout output differs from expected:
--- codeGen/should_compile/T14999.run/T14999.stdout.normalised  2021-03-04 13:28:51.648586079 -0500
+++ codeGen/should_compile/T14999.run/T14999.run.stdout.normalised      2021-03-04 13:28:51.648586079 -0500
@@ -1,6 +1,6 @@
 Dump of assembler code for function stg_catch_frame_info:
- 0x0000000000000010 <+0>:      add $0x18,%rbp
- 0x0000000000000014 <+4>:      jmpq *0x0(%rbp)
+ 0x0000000000000010 <+1>:      add $0x18,%rbp
+ 0x0000000000000014 <+5>:      jmpq *0x0(%rbp)
 End of assembler dump.
 Contents of the .debug_frame section:
 00000000 0000000000000014 ffffffff CIE "" cf=1 df=-8 ra=16
*** unexpected failure for T14999(normal)

Performance Metrics (test environment: local):


None collected.


Unexpected results from:
TEST="T14999"

SUMMARY for test run started at Thu Mar  4 13:28:51 2021 
0:00:00.392025 spent to go through
       1 total tests, which gave rise to
      10 test cases, of which
       6 were skipped

       0 had missing libraries
       0 expected passes
       0 expected failures

       0 caused framework failures
       0 caused framework warnings
       0 unexpected passes
       1 unexpected failures
       0 unexpected stat failures
       0 fragile tests

Unexpected failures:
   codeGen/should_compile/T14999.run  T14999 [bad stdout] (normal)

Since this failure doesn't occur on CI, I can only assume that this depends on something specific to quick.

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