chromatic wrote:
On Saturday 17 March 2007 05:47, James Keenan via RT wrote:
On #parrot, Jonathan indicated this test is expected to fail. If there is
no spec clarification by the end of today's Bug Day, it will be TODO-ed.
No more expected failures that are not TODOs.
I think that's a good idea, yes.
We've wasting enough volunteer time trying to debug expected failures.
Turns out I'm one volunteer who's been trying to get this resolved. In
fact, there were more failing tests in that file that I worked to
resolve already. If you look in the test file, there's comments that
make it clear that the issue is a question on the spec. Perhaps I
shoulda marked the test todo earlier on when I knew I was waiting on an
answer to what the correct behavior should have been.
We have TODO tests for a reason--so if you know a test will fail and you check
it in anyway, make it a TODO test. The rest of us can't read your mind.
Not to pass the buck or anything, but it wasn't me that wrote and
checked in the test in the first place, I'm just working on the issue
raised by the test. I'd prefer that you just ranted about issues rather
than at/about individuals, but if you must at least bother to figure out
who to rant at.
Jonathan
