Tests failing due to different type variables in the diagnostics
A couple of tests fail unexpectedly because some type variables are printed a0
rather than the expected a
:
Actual stderr output differs from expected:
--- ./rebindable/DoParamM.stderr.normalised 2011-04-02 16:59:19.000000000 +0200
+++ ./rebindable/DoParamM.comp.stderr.normalised 2011-04-02 16:59:19.000000000 +0200
@@ -7,7 +7,7 @@
DoParamM.hs:286:28:
Couldn't match expected type `Locked' with actual type `Unlocked'
- Expected type: LIO Locked r b
+ Expected type: LIO Locked r0 b0
Actual type: LIO Unlocked Locked ()
In the expression: tlock2_do
In the expression:
@@ -16,7 +16,7 @@
DoParamM.hs:302:37:
Couldn't match expected type `Unlocked' with actual type `Locked'
- Expected type: LIO Unlocked r b
+ Expected type: LIO Unlocked r0 b0
Actual type: LIO Locked Unlocked ()
In the expression: unlock
In the expression:
*** unexpected failure for DoParamM(normal)
Actual stderr output differs from expected:
--- ./driver/recomp006/recomp006.stderr.normalised 2011-04-02 19:06:18.000000000 +0200
+++ ./driver/recomp006/recomp006.run.stderr.normalised 2011-04-02 19:06:18.000000000 +0200
@@ -8,7 +8,7 @@
In an equation for `f': f = (1, (2, 3))
A.hs:8:8:
- Couldn't match expected type `Int' with actual type `(t, t1)'
+ Couldn't match expected type `Int' with actual type `(t0, t1)'
In the expression: (2, 3)
In the expression: (1, (2, 3))
In an equation for `f': f = (1, (2, 3))
*** unexpected failure for recomp006(normal)
Actual stderr output differs from expected:
--- ./ghc-api/apirecomp001/apirecomp001.stderr.normalised 2011-04-02 19:08:46.000000000 +0200
+++ ./ghc-api/apirecomp001/apirecomp001.run.stderr.normalised 2011-04-02 19:08:46.000000000 +0200
@@ -5,9 +5,9 @@
B.hs:5:12:
Warning: Defaulting the following constraint(s) to type `Integer'
- (Enum a) arising from the arithmetic sequence `1 .. 23 * 2'
+ (Enum a0) arising from the arithmetic sequence `1 .. 23 * 2'
at B.hs:5:12-20
- (Num a) arising from the literal `1' at B.hs:5:13
+ (Num a0) arising from the literal `2' at B.hs:5:19
In the first argument of `length', namely `[1 .. 23 * 2]'
In the first argument of `(-)', namely `length [1 .. 23 * 2]'
In the expression: length [1 .. 23 * 2] - 4
@@ -21,9 +21,9 @@
B.hs:5:12:
Warning: Defaulting the following constraint(s) to type `Integer'
- (Enum a) arising from the arithmetic sequence `1 .. 23 * 2'
+ (Enum a0) arising from the arithmetic sequence `1 .. 23 * 2'
at B.hs:5:12-20
- (Num a) arising from the literal `1' at B.hs:5:13
+ (Num a0) arising from the literal `2' at B.hs:5:19
In the first argument of `length', namely `[1 .. 23 * 2]'
In the first argument of `(-)', namely `length [1 .. 23 * 2]'
In the expression: length [1 .. 23 * 2] - 4
*** unexpected failure for apirecomp001(normal)
In apirecomp001
, also the literal triggering the message is different. That's probably due to the new type checker, if the behaviour is stable, the expected stderr output should be adjusted.
Trac metadata
Trac field | Value |
---|---|
Version | 7.0.3 |
Type | Bug |
TypeOfFailure | OtherFailure |
Priority | normal |
Resolution | Unresolved |
Component | Test Suite |
Test case | |
Differential revisions | |
BlockedBy | |
Related | |
Blocking | |
CC | |
Operating system | |
Architecture |