Thread overview | ||||||
---|---|---|---|---|---|---|
|
July 03, 2012 [dmd-internals] fail_compilation/fail108.d | ||||
---|---|---|---|---|
| ||||
It looks like this test is now hanging on every build attempt across at least linux and freebsd. The auto-tester,
thusly stalls on pretty much every test run (be it mainline or pull request). I don't have the time right now to do
anything about it, so the tester is kinda dead until that's fixed and I can sweep through the machines killing the failures.
If someone wants to help the most, adding a timeout alarm to d_do_test to kill any test that runs for more than, say, 15 minutes (way way longer than any test currently runs) would be great.
Thanks,
Brad
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals
|
July 03, 2012 Re: [dmd-internals] fail_compilation/fail108.d | ||||
---|---|---|---|---|
| ||||
Posted in reply to Brad Roberts | On Windows, this test generates a stack overflow fault. On 7/3/2012 10:04 AM, Brad Roberts wrote: > It looks like this test is now hanging on every build attempt across at least linux and freebsd. The auto-tester, > thusly stalls on pretty much every test run (be it mainline or pull request). I don't have the time right now to do > anything about it, so the tester is kinda dead until that's fixed and I can sweep through the machines killing the failures. > > If someone wants to help the most, adding a timeout alarm to d_do_test to kill any test that runs for more than, say, 15 > minutes (way way longer than any test currently runs) would be great. > > Thanks, > Brad > _______________________________________________ dmd-internals mailing list dmd-internals@puremagic.com http://lists.puremagic.com/mailman/listinfo/dmd-internals |
July 03, 2012 Re: [dmd-internals] fail_compilation/fail108.d | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | os/x is also hanging. So that's everything is broken, right? A rather seroius regression so please revert whatever change was just checked in that caused it and I'll kick the fleet of auto-testers back into life. On Tue, 3 Jul 2012, Walter Bright wrote: > On Windows, this test generates a stack overflow fault. > > On 7/3/2012 10:04 AM, Brad Roberts wrote: > > It looks like this test is now hanging on every build attempt across at > > least linux and freebsd. The auto-tester, > > thusly stalls on pretty much every test run (be it mainline or pull > > request). I don't have the time right now to do > > anything about it, so the tester is kinda dead until that's fixed and I can > > sweep through the machines killing the failures. > > > > If someone wants to help the most, adding a timeout alarm to d_do_test to > > kill any test that runs for more than, say, 15 > > minutes (way way longer than any test currently runs) would be great. > > > > Thanks, > > Brad > > > > _______________________________________________ > dmd-internals mailing list > dmd-internals@puremagic.com > http://lists.puremagic.com/mailman/listinfo/dmd-internals > _______________________________________________ dmd-internals mailing list dmd-internals@puremagic.com http://lists.puremagic.com/mailman/listinfo/dmd-internals |
July 03, 2012 Re: [dmd-internals] fail_compilation/fail108.d | ||||
---|---|---|---|---|
| ||||
Posted in reply to Brad Roberts | Fixed. On 7/3/2012 1:59 PM, Brad Roberts wrote: > os/x is also hanging. So that's everything is broken, right? A rather > seroius regression so please revert whatever change was just checked in > that caused it and I'll kick the fleet of auto-testers back into life. > > > On Tue, 3 Jul 2012, Walter Bright wrote: > >> On Windows, this test generates a stack overflow fault. >> >> On 7/3/2012 10:04 AM, Brad Roberts wrote: >>> It looks like this test is now hanging on every build attempt across at >>> least linux and freebsd. The auto-tester, >>> thusly stalls on pretty much every test run (be it mainline or pull >>> request). I don't have the time right now to do >>> anything about it, so the tester is kinda dead until that's fixed and I can >>> sweep through the machines killing the failures. >>> >>> If someone wants to help the most, adding a timeout alarm to d_do_test to >>> kill any test that runs for more than, say, 15 >>> minutes (way way longer than any test currently runs) would be great. >>> >>> Thanks, >>> Brad >>> >> _______________________________________________ >> dmd-internals mailing list >> dmd-internals@puremagic.com >> http://lists.puremagic.com/mailman/listinfo/dmd-internals >> > _______________________________________________ > dmd-internals mailing list > dmd-internals@puremagic.com > http://lists.puremagic.com/mailman/listinfo/dmd-internals > > _______________________________________________ dmd-internals mailing list dmd-internals@puremagic.com http://lists.puremagic.com/mailman/listinfo/dmd-internals |
Copyright © 1999-2021 by the D Language Foundation