PLEASE comment out the failing tests while you work on it. Reason being, that it means that other people cannot tell if a change they've checked in has broken the tests. This affects Phobos, druntime, and the compiler. You should take the view that all development is blocked while it's broken. It is OK to break the tests (it would be useless if it never failed!) But if it fails, get it working again ASAP by whatever means necessary (including reverting the commit, or in the worst case, commenting out tests).
On 13 January 2011 08:52, Jonathan M Davis <[email protected]> wrote: > Well, the Phobos unittest build continues to fail by running out of memory. > I'm > really quite stumped by it. Running it in Linux, I don't think that it ever > goes > much above 100MB, and most of the time, its memory consumption is considerably > less. However, on Windows, it goes above 900MB and decides that its run out of > memory. > > The problem does appear to be in std.datetime, since if I comment out the > module, it's fine. If I comment out a large portion of the unit tests, it's > fine, > but I get the impression that it's due to the large number of unit tests > rather > than any particular test. Maybe it's due to the templated test functions I'm > using taking up too much memory which isn't released? There _is_ at least one > bug relating to memory not being released during CTFE. > > However, to make matters even more interesting, when I ran the unittest build > in > wine, it didn't have any memory problems. I think that it might have hit > around > 300MB, which is more than the Linux build got to, but it certainly wasn't in > excess of 900MB. So, I'm rather stumped as to what to do about it. > > - Jonathan M Davis > _______________________________________________ > phobos mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/phobos > _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
