Martin Pool wrote:
> Public bug reported:
>
>>From talking to John about bug 415508: record_entry_contents has some
> tests that check it records data when it should but (I think) no tests
> that it doesn't store data when it shouldn't - so you can get the kind
> of misbehaviour reported by Frits.
Well, even beyond 'record_entry_contents', commit in general doesn't
have any of these tests.
So while we are quite confident that things that should be there are
present (we would get bug reports, breakage, etc if that wasn't the
case). If we add too much, it just doesn't show up.
In Frits's case, this is exacerbated by the fact that "bzr log -v"
doesn't show these modifications, even though "bzr log -v FILE" *does*.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Pool wrote: entry_contents has some
> Public bug reported:
>
>>From talking to John about bug 415508: record_
> tests that check it records data when it should but (I think) no tests
> that it doesn't store data when it shouldn't - so you can get the kind
> of misbehaviour reported by Frits.
Well, even beyond 'record_ entry_contents' , commit in general doesn't
have any of these tests.
So while we are quite confident that things that should be there are
present (we would get bug reports, breakage, etc if that wasn't the
case). If we add too much, it just doesn't show up.
In Frits's case, this is exacerbated by the fact that "bzr log -v"
doesn't show these modifications, even though "bzr log -v FILE" *does*.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
VREcACgkQJdeBCY SNAANUbgCg2fybc F0WMUvAj76PBpVk NzXX FF6sXMG3ZtrgQ4y Xj
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq
vGgAoLZnbu0MCSd
=KOnZ
-----END PGP SIGNATURE-----