Breaking the Travis CI build is pretty easy to do and also pretty common. Never fear! It is also easy to fix.
Each pull request page indicates whether your commits have errors that break the build.
Next to the failing build message is a Details link. Click it to find out what's causing the failure. It will take you to a page at Travis-CI.org. Scroll down that page until you see a bunch of red text.
This will indicate what error, what file, and what line is causing a problem. Note: The exact error text will vary depending on which language you are using.
If you are adding content via Markdown files, HTML-Proofer will report errors in the generated HTML files. You'll need to fix the error in the corresponding Markdown file.
Common causes of a failing build are HTML markup errors, HTML entity errors, and broken links. Below are some common error messages, their causes, and their fixes.
| If you see an error like this… | It's probably caused by… | To fix, do… |
|---|---|---|
Unexpected end tag |
Mismatched tags. Either the end tag is wrong (e.g. <h4>Heading</h6>), or the start tag is missing altogether. (e.g. Heading</h6>) |
Check the corresponding Markdown file for that HTML page. |
htmlParseEntityRef: expecting ';' |
An unescaped character. Some characters need to be escaped in HTML using a named character reference. Such characters include &, >, " and <. |
Use an named character reference for the character in question. |
* internally linking to [path], which does not exist |
Either there's (a) an explicit link to the wrong file, or (b) a generated breadcrumb link points to a page that doesn't exist. | If (a), fix your URLs to point to the right page. If (b), update your directory structure. See How URLs are Created for more. |