Subject: | bad Wheel::Run test |
<+LotR> now to figure out why Loop::Glib fails one Wheel::Run test and
hangs in the signals_rerun tests
<+LotR> # Callback timing is different for Gtk.
<+LotR> $heap->{flushes_expected}++ if (
<+LotR> exists $INC{'Gtk.pm'} and $heap->{label} eq
'string/pause_resume'
<+LotR> );
<+LotR> that might be cause of the Wheel::Run one
<+LotR> dngor: you remember this:
http://poe.svn.sourceforge.net/viewvc/poe?view=rev&revision=2092
<+LotR> how did you check Gtk wasn't just doing something wrong?
<@dngor> If I recall correctly, it was after a few hours of debugging.
<@dngor> That change compromises the tests. I'd prefer a better fix.
* LotR s/hours/weeks/ for the guestimate on when he'll understand stuff
sufficiently to come up with something
<+LotR> (hehe, using s/// as a verb doesn't seem to work well)
<@dngor> Well, does including Glib in that "fix" the test?
<+LotR> yes
<@dngor> Hm.
<+nopaste> Someone at 62.131.36.85 pasted "not ok 99 -
string/pause_resum" (18 lines) at http://nopaste.snit.ch:8001/10858
<@dngor> File a bug against the test. Maybe a fresh look will come up
with a better fix.