-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netlify build fails early with no info #179
Comments
I've seen some hard exits when a tap reporter can't handle the tap stream somehow. In case you're running a reporter on the output stream, try instead to pipe the raw tap output to a file. It's more verbose, but should give better insights into what's going on. If it's hyperlink itself that explodes, then it's a bit more tricky and I'll have to recreate and inspect with breakpoints |
Ah hmm—I can pipe it to a file but it’s tricky to access that file when it resides on the build server. It has happened fairly regularly that it fails on the build server but not locally (even after clearing out my _site folder and re-running) |
Is the output better if you enable link checking through https://www.npmjs.com/package/netlify-plugin-checklinks and the netlify build beta? |
Terminal output is quite noisy now but it looks like this was causing our flaky checks. See related issue Munter/hyperlink#179
I have a failing link on the link checker but I have no insight into what it is! It doesn’t show up locally and the Netlify build quits early so it never gives the final report.
While this is partially Netlify’s fault https://community.netlify.com/t/common-issue-deploy-logs-truncated-or-showing-shutting-down-logging-number-messages-pending/747 I did play around with verbose mode locally but it doesn’t seem to output the links that are checking while they’re being checked.
Is there any way to improve the output here so that it shows the failing link when it finds it?
The text was updated successfully, but these errors were encountered: