Skip to content
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

test lighthousebot pr auto comment #14

Closed
wants to merge 4 commits into from

Conversation

bronz3beard
Copy link
Contributor

Testing lighthouse-bot pr comment automation pr will be deleted after testing.

@bronz3beard
Copy link
Contributor Author

@camposcristianeze

Currently there is an issue with lighthouse-bot.

This is the response from the on-success of the travis.yml "job log"
lighthouse-bot error:
yarn run v1.15.2
$ lighthousebot -- --pwa=95 --perf=95 --seo=95 --a11y=95 --bp=95 https://website-ssr-pr-20.herokuapp.com/
Using runner: chrome
New Lighthouse scores:
"Error from CI backend. invalid json response body at https://builder-dot-lighthouse-ci.appspot.com/ci
reason: Unexpected token U in JSON at position 0"
Done. Your build exited with 0.

When visiting this link it mentions it needs credentials, just want to double check, does travis have the env var for lighthosue-bot?

I have submitted an issue to see if i can get some answer regarding the error, I found a similar error in the issues but no resolutions so submitted my own..

@camposcristian
Copy link
Contributor

Ok, to be honest I'm not sure what can be happening here, but def this url: https://builder-dot-lighthouse-ci.appspot.com/ci is expecting an API call instead of a browser GET so that's might the reason why visiting the url is not working.

What you could also try is running that lh command on localhost and check if you have any other clues

@kbardi kbardi deleted the feature/test-lighthousebot-pr-comment branch March 9, 2020 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants