On 18 joulu, 19:56, Julien Phalip <jpha...@gmail.com> wrote:
> On Dec 18, 2012, at 5:18 AM, Emil Stenström <e...@kth.se> wrote:
>
> > On Monday, 2 June 2008 02:45:07 UTC+2, Ludvig Ericson wrote:
> > I'd rather see this be leaved as-is, since I haven't seen a single
> > report on these broken pipe 'issues'.
>
> > Here's a report:
>
> > I'm using PhantomJS (headless webkit browser) to test for javascript errors 
> > on my site. Using the LiveServerTestCase it's possible to spawn a test 
> > server, and using Python's subprocess I can call PhantomJS to access that 
> > server and assert that there are no errors.
>
> > Problem is, the test server is spitting back broken pipe errors. By reading 
> > explanations elsewhere I've understood that this is a browser problem, that 
> > they are not supposed to break connections like that, but the fact is that 
> > they are. It feels strange to read recommendations that I should just 
> > ignore the errors, since having random stacktrace printouts in my tests 
> > feels extremely sloppy.
>
> > Given that browsers behave like they do, and we're not able to change that, 
> > I suggest that ticket #4444 is reconsidered, and no marked as wontfix.
>
> > As a workaround I would have hoped for a way to ignore the messages in some 
> > other way. I've tried setting up logging to ignore the errors, but failed. 
> > My guess is that these errors don't go through the logger. Maybe this 
> > couple me the recommended (and documented) way of handling this?
>
> > (Here's the code if you want to 
> > reproduce:http://stackoverflow.com/questions/13287490/is-there-a-way-to-use-pha...)
>
> Those errors are indeed extremely noisy and confusing. I'm in favor of 
> modifying Django to reduce that noise, but only if it gets proven that 
> ignoring those errors won't either cause the tests to fail or to pass as 
> false positives.

I haven't yet to see any useful data in the broken pipe errors. I am
in favour of silencing or just reporting "Broken pipe" without
stacktrace.

Does anybody know of situations where silencing the broken pipe errors
would lead to missing actual errors?

 - Anssi

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to