Shortening the failed link output

[AnnaDinaburgVulikh]

Hi, when a failed link is found a short log of the failed link is shown but after that comes a very long log of all the functions that failed in the process.

Would be happy to help with the fix if you can point me in the right direction.

[AnnaDinaburgVulikh]

@blink1073 can you give me some pointers for fixing this?

[afshin]

Is this a byproduct of the native stack traces in Python?

I am not sure how to resolve this in a way that doesn't obscure information needed to debug.

[AnnaDinaburgVulikh]

It's odd, but I couldn't reproduce this on my machine right now.
When I opened this issue I got an error for some links and an output of all the functions the project uses to check the links.
Ran it 3 times right now and everything looks OK.

[AnnaDinaburgVulikh]

@afshin , got the long log again, you can see it below.
Tried the site manually, everything seems to work, but the test fails.
Can you help?

link-error.log

[afshin]

I am not sure what is happening @AnnaDinaburgVulikh, but I wonder if it has to do with the fact that that URL is a 2.1 megabyte download ... which might explain the intermittent nature of the failure. It's a very large HTML file because it has images that are base64 encoded and included as data URLs for image tags within the file.

[AnnaDinaburgVulikh]

As I see it, there are 2 questions inferred :

1. Is all the log relevant, or it might be shorter ? If so, where can I tackle it.
2. Is there a way to override the default timeout?