Matthew Hambley <email@example.com> writes:
> Right, this is driving me spare!
> Due to the thundering silence which met my request for help with my patch
> I've been blundering around in the build process trying to figure it out
> for myself. I've solved the problem of my unit tests not being run by
> 'make check'. (although I'm not entirely sure how) Unfortunately this has
> thrown up a new problem. My patch doesn't break subversion (as far as I
> know) but it does break the tests. Now that every file is given a MIME
> type property tests which do not expect it to have one are failing.
> So now I can't work out how to modify the tests to deal with this. I've
> tried every permutation I can think of but always with the same result.
> Something somewhere complains that either it was expecting the property but
> didn't find it or that it found the property but wasn't expecting it.
> Where should I put this information so that those stages which don't find
> it don't expect it and those which do, do?
Your patch itself was not greeted with thundering silence, though. It
was filed as issue #1233, and I added some commentary there which
might explain the lack of help in fixing the tests, basically saying
that the extra complexity wasn't worth the added functionality for
pre-1.0. I'm not claiming that everyone agrees with that assessment
-- merely that no one appears to disagree strongly enough to volunteer
By the way, your mail above references neither the issue number, nor
the mailing list archive URL for the mail in which you requested help,
and describes the patch in question only by implication. This doesn't
make it easy for people to help, even those who want to.
I don't know what to say about the property tests. It might be better
if you post describing how one (small) test fails, and how you tried
to make it pass, and what resulted. Generic descriptions like the
above don't really help anyone help you, it just informs them that
your having a problem.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Apr 27 02:35:23 2003