CI Tests for markdown broken
Closed this issue · 1 comments
staubesv commented
Describe the bug
All builds currently fail because there are markdown documentation not following the conventions expectecd by markdownlint.
To Reproduce
- $ npm run markdownlint
Actual Behavior
Tests are broken:
$ npm run markdownlint
> paellaplayer@6.0.4 markdownlint /home/travis/build/polimediaupv/paella
> markdownlint ./doc/
doc/developers/plugin_creation.md: 51: MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```javascript"]
doc/developers/plugin_creation.md: 62: MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```javascript"]
doc/developers/plugin_creation.md: 105: MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
doc/examples/es.upv.paella.hlsPlayer.md: 13: MD001/heading-increment/header-increment Heading levels should only increment by one level at a time [Expected: h2; Actual: h3]
doc/examples/es.upv.paella.hlsPlayer.md: 26: MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
doc/examples/es.upv.paella.hlsPlayer.md: 36: MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```"]
doc/examples/es.upv.paella.hlsPlayer.md: 60: MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
doc/examples/es.upv.paella.hlsPlayer.md: 84: MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
doc/examples/es.upv.paella.hlsPlayer.md: 359: MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
doc/examples/es.upv.paella.hlsPlayer.md: 395: MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! paellaplayer@6.0.4 markdownlint: `markdownlint ./doc/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the paellaplayer@6.0.4 markdownlint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/travis/.npm/_logs/2019-02-25T14_16_54_808Z-debug.log
Expected behavior
Tests should work.