-
Notifications
You must be signed in to change notification settings - Fork 350
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
Infrastructure: Fix failing npm run regression-report
script
#2291
Conversation
b27c712
to
dd13ac1
Compare
dd13ac1
to
373ef16
Compare
373ef16
to
6c119fc
Compare
@mcking65 this has been updated following #2837. The result of npm run regression-report now gives me:
|
e2789ed
to
6a83aac
Compare
@howard-e it may be the separate issue but I have error of missing script:"regression-report" when I did npm run regression-report. When I check the available list of script using "npm run", fmt, lint, and boostrap were only available. I am mentioning @spectranaut in case she can help. |
@a11ydoer when I do npm run result❯ npm run
Lifecycle scripts included in [email protected]:
test
npm run lint && npm run regression
available via `npm run-script`:
fix
npm run lint:es -- --fix && stylelint --fix "**/*.css" && prettier --write "**/*.css"
htmlhint
htmlhint "**/*.html" "**/*.template" --ignore "common/**/*.html" --format unix
lint
npm run lint:es && npm run lint:css && npm run lint:html && npm run lint:spelling
lint:css
stylelint "**/*.css" && prettier --check "**/*.css"
lint:es
eslint . --report-unused-disable-directives
lint:js
npm run lint:es
lint:html
npm run htmlhint && npm run vnu-jar
lint:spelling
cspell "**/*.*"
link-checker
node ./scripts/link-checker.js
reference-tables
node scripts/reference-tables.js
regression
ava --timeout=1m
regression-report
node test/util/report
vnu-jar
java -jar node_modules/vnu-jar/build/dist/vnu.jar --filterfile .vnurc --no-langdetect --skip-non-html content/
create-gh-project
node ./scripts/create-gh-project.js
prepare
husky install I'm not familiar with the |
@howard-e sorry. you are right. this is downside of multi-tasking, not focusing on one thing. I was using old repo not updated one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"npm run regression-report" is working due to directory path update.
@@ -7,7 +7,7 @@ const fs = require('fs'); | |||
const htmlparser2 = require('htmlparser2'); | |||
const spawn = require('cross-spawn'); | |||
|
|||
const examplePath = path.resolve(__dirname, '..', '..', 'examples'); | |||
const examplePath = path.resolve(__dirname, '..', '..', 'content', 'patterns'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@howard-e yes, updated path info was what I needed to run regression test. Thanks. I will also check other changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@howard-e I confirmed that the path update here works. Thanks again!
I am getting a runtime error as follows.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @howard-e! This is now working.
Address comments in #959.
cc @nschonni
WAI Preview Link