On 3/7/2011 2:37 PM, John A Meinel wrote:
> I have a branch which should fix this, but so far, I have been unable to
> reproduce the failure.
>
> Note that some of the HEAD changes have landed in loggerhead, so it is
> possible this is hiding the original GeneratorExit failure.
>
So I do have a test case that reproduced getting an OOPS from
GeneratorExit, and that it is appropriately squashed and replaced with a
log message.
However, I wasn't able to manually trigger such a GeneratorExit via the
HTTP interface of a running dev system.
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
On 3/7/2011 2:37 PM, John A Meinel wrote:
> I have a branch which should fix this, but so far, I have been unable to
> reproduce the failure.
>
> Note that some of the HEAD changes have landed in loggerhead, so it is
> possible this is hiding the original GeneratorExit failure.
>
So I do have a test case that reproduced getting an OOPS from
GeneratorExit, and that it is appropriately squashed and replaced with a
log message.
However, I wasn't able to manually trigger such a GeneratorExit via the
HTTP interface of a running dev system.
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAk1 04m0ACgkQJdeBCY SNAAPO9wCffId9C NDi5Du5WjRUflBM LkbA 2jZ4IhhFGCakez7 9YNbNJCPzZ
sbwAni/
=67P+
-----END PGP SIGNATURE-----