Bug 16227 – std.numeric unit tests fail when run in isolation

Status
RESOLVED
Resolution
FIXED
Severity
minor
Priority
P1
Component
phobos
Product
D
Version
D2
Platform
x86_64
OS
Linux
Creation time
2016-07-02T09:16:00Z
Last change time
2016-12-27T13:45:42Z
Assigned to
nobody
Creator
atila.neves

Comments

Comment #0 by atila.neves — 2016-07-02T09:16:00Z
make -f posix.mak unittest-debug # fine make -f posix.mak std/numeric.test core.exception.AssertError@std/numeric.d(1955): unittest failure
Comment #1 by tjfryan — 2016-07-12T07:35:47Z
Throwing `writeln(!e);` before the `if (!e) continue;` on line 1943 of numeric.d somehow got the unittest to pass. What's more interesting is that every time the continue is taken, !e is reported to be false.
Comment #2 by greeenify — 2016-07-18T17:46:22Z
Comment #3 by greeenify — 2016-07-18T17:47:11Z
*** Issue 16259 has been marked as a duplicate of this issue. ***
Comment #4 by greensunny12 — 2016-08-25T12:43:00Z
Just for completeness this also affects std.algorithm.sorting and has been reported by Andrei in the NG: http://forum.dlang.org/post/[email protected] And a bit later by John: http://forum.dlang.org/post/[email protected] For the code coverage we temporarily exclude std.algorithm.sorting: https://github.com/dlang/phobos/pull/4587
Comment #5 by greeenify — 2016-12-27T13:45:42Z
This has been fixed since a while thanks to the cycle detection in druntime.