Opened 3 years ago

Closed 21 months ago

#12712 closed bug (fixed)

break011 is broken on Windows

Reported by: bgamari Owned by:
Priority: normal Milestone: 8.4.1
Component: Test Suite Version: 8.0.1
Keywords: Cc: Phyx-
Operating System: Windows Architecture: x86_64 (amd64)
Type of failure: None/Unknown Test Case: break011
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:

Description

The break011 testcase fails on Windows with some unexpected differences in stdout.

+++ ./ghci.debugger/scripts/break011.run/break011.run.stdout.normalised 2016-10-16 01:57:26.489544400 +0000
@@ -51,6 +51,9 @@
                        "foo"
                        "CallStack (from HasCallStack):
   error, called at Test7.hs:<line>:<column> in <package-id>:Main")
-*** Exception: foo
-CallStack (from HasCallStack):
-  error, called at Test7.hs:<line>:<column> in <package-id>:Main
+Stopped in <exception thrown>, <unknown>
+_exception :: e = SomeException
+                    (ErrorCallWithLocation
+                       "foo"
+                       "CallStack (from HasCallStack):
+  error, called at Test7.hs:<line>:<column> in <package-id>:Main")

Change History (6)

comment:1 Changed 3 years ago by bgamari

I'm going to mark this test as expect_broken for now.

comment:2 Changed 3 years ago by bgamari

Architecture: Unknown/Multiplex86_64 (amd64)
Operating System: Unknown/MultipleWindows

comment:3 Changed 3 years ago by Ben Gamari <ben@…>

In deed4189/ghc:

testsuite: Mark break011 as broken

See #12712.

comment:4 Changed 3 years ago by bgamari

Milestone: 8.2.18.4.1

Given that 8.2.1-rc1 is imminent, I'm bumping these off to the 8.4

comment:5 Changed 23 months ago by bgamari

Milestone: 8.4.18.6.1

This ticket won't be resolved in 8.4; remilestoning for 8.6. Do holler if you are affected by this or would otherwise like to work on it.

comment:6 Changed 21 months ago by bgamari

Milestone: 8.6.18.4.1
Resolution: fixed
Status: newclosed

It looks like this was fixed in 7af0b906116e13fbd90f43f2f6c6b826df2dca77. Yay!

Note: See TracTickets for help on using tickets.