Thanks for that report, Matt. I saw a very similar error when I tried to remove the threading subsystem entirely in a branch. I saw the same failures as you are seeing, but not initially. This suggests to me that some recent modifications and cleanups in the Timer PMC and elsewhere might have created an unintentional dependency on some of the threading code.
I'll take a long look at this today and tonight if possible. --Andrew Whitworth On Mon, Sep 19, 2011 at 1:10 PM, Matthew Boyle <[email protected]> wrote: > On 16/09/11 03:38, Kevin Polulak wrote: >> >> If you do encounter any test failures, make some noise here on >> parrot-dev and on #parrot. > > I've been seeing consistent errors in t/pmc/timer.t when building > --without-threads: > <http://smolder.parrot.org/app/projects/report_details/23294> (with GCC) or > <http://smolder.parrot.org/app/projects/report_details/23297> (with Clang). > > I've not had a chance to properly investigate this, but a quick bit of > experimenting suggests that the Timer isn't executing the 'tick' callback at > all. > > All tests pass when built with threads. > > --matt > > > -- > Matthew Boyle, Systems Administrator, CoreFiling Limited > Telephone: +44-1865-203192 Website: http://www.corefiling.com > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
