Lighthouse-ci: Status checks not set properly when using Github Actions

[thomkrupa]

Hey,

I use Github Actions as CI. I set up a Github Token through secrets, everything works well except setting status, it fails with Invalid repo slug "undefined", skipping.

lgci autorun logs:

✅  .lighthouseci/ directory writable
✅  Ancestor hash determinable
Healthcheck passed!

Automatically determined ./public as `staticDistDir`.
Set it explicitly in lighthouserc.json if incorrect.

Started a web server on port 33093...
Running Lighthouse 3 time(s) on http://localhost:33093/index.html
Run #1...done.
Run #2...done.
Run #3...done.
Done running Lighthouse!

Uploading median LHR of http://localhost:33093/index.html...success!
Open the report at https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1573513709814-41442.report.html
GitHub token found, attempting to set status...
Invalid repo slug "undefined", skipping.
Done running autorun.

[patrickhulce]

Ah thanks very much @thomkrupa! We didn't expect folks to want to use both in combination :)

We'll fix ASAP though 👍

[ReddytoRumble]

@patrickhulce I'm running into the same error when running this on Jenkins. Everything seems to work well until it attempts to set a status. It's unclear from the error message what the problem is.
Any thoughts on what could be wrong?

10:09:30 ✅ .lighthouseci/ directory writable 10:09:30 ✅ Configuration file found 10:09:30 ✅ Chrome installation found 10:09:30 ✅ GitHub token set 10:09:30 Healthcheck passed! 10:09:30 10:09:31 Running Lighthouse 3 time(s) on https://qa.mydomain.com 10:09:46 Run #1...done. 10:09:58 Run #2...done. 10:10:10 Run #3...done. 10:11:45 Done running Lighthouse! 10:11:45 10:11:45 Saving CI project mydomain.com (0bf81f32-ecea-4426-97d2-453733430d09) 10:11:45 Saving CI build (45e067a2-0b52-45ab-9dd9-49c6d192b6c3) 10:11:45 Saved LHR to http://10.102.5.4:9001 (e5bac366-35ba-4a80-a025-2022197d8a3e) 10:11:45 Saved LHR to http://10.102.5.4:9001 (4d20fd2b-1a28-43e4-99ec-5349b1044d62) 10:11:45 Saved LHR to http://10.102.5.4:9001 (71ec351c-35bf-4448-ae7f-d52355c919fd) 10:11:45 Saved LHR to http://10.102.5.4:9001 (745da1ee-f0d8-4657-a7ff-79880742100a) 10:11:45 Saved LHR to http://10.102.5.4:9001 (c7839133-7d5a-4e51-9083-af1c61a92668) 10:11:45 Saved LHR to http://10.102.5.4:9001 (61af79f3-46da-4001-bfdb-e66908b22e21) 10:11:45 Saved LHR to http://10.102.5.4:9001 (47f27850-5d2a-468b-831e-afc1799ec013) 10:11:45 Saved LHR to http://10.102.5.4:9001 (71f2f1cf-ff8c-4d7e-96cb-c8c11febdf5f) 10:11:45 Saved LHR to http://10.102.5.4:9001 (316388b3-db46-4631-ab58-40f4fcb9deb6) 10:11:45 Done saving build results to Lighthouse CI 10:11:45 View build diff at http://10.102.5.4:9001/app/projects/mydomain.com/compare/45e067a2-0b52-45ab-9dd9-49c6d192b6c3 10:11:45 GitHub token found, attempting to set status... 10:11:45 Invalid repo slug "undefined", skipping.

[patrickhulce]

@ReddytoRumble are you using a private GitHub instance by chance? The status check won't work with anything other than public GitHub right now (private GH tracked by #92)

Also since you're using Jenkins we don't automatically know what the repo is yet (tracked by same work as #88) so you'd need to manually tell lhci what it is.

example:

export LHCI_BUILD_CONTEXT__GITHUB_REPO_SLUG=GoogleChrome/lighthouse-ci

[ReddytoRumble]

@patrickhulce Thanks for the tip. I'm not using a private Github Instance. Your suggestion to set the LHCI_BUILD_CONTEXT__GITHUB_REPO_SLUG variable worked for me. Thank you 🙏