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

Lighthouse verification step passes with error #99

Closed
marklaatikainen opened this issue Jul 13, 2022 · 6 comments
Closed

Lighthouse verification step passes with error #99

marklaatikainen opened this issue Jul 13, 2022 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@marklaatikainen
Copy link

Describe the bug
Step passes with runtime error

To Reproduce
Run check against url that loads slowly

Expected behavior
Step should fail if page could not load

Additional context
Our webstore preview link takes long time to load on first load after it was built. Step passes still with SUCCESS when it has runtimeError

lighthouseCheckResults: {"code":"SUCCESS","data":[{"url":"webstore-preview-url","emulatedFormFactor":"desktop","runtimeError":"The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP)","scores":{}}]}

Actual result
lighthouse-check: Scores passed minimum requirement ✅

@adamhenson
Copy link
Collaborator

adamhenson commented Jul 13, 2022

@marklaatikainen - could you please update this issue to provide more details in the "To Reproduce" section and "Expected behavior" section? It looks like you provided the output of the GitHub Action which looks correct.

Please provide your configuration or some similar example configuration. I would expect there to be no scores in the output and an error message per this recent PR. Do you not see an error message logged in the output?

Is the problem that you are using foo-software/lighthouse-check-status-action and the workflow doesn't fail when you would expect it to? If so, you would definitely need to at least specify the relevant configuration for that (it's actually a different GitHub Action altogether... but it is related to this, so we can keep this open).

Regardless, I will need a minimal example and more information to understand the issue better.

@marklaatikainen
Copy link
Author

image

Configuration looks like this. There are separate jobs for desktop and mobile, with different minimum scores.

It gives following output and passes both steps:

image

@adamhenson
Copy link
Collaborator

I see... thank you @marklaatikainen. As I suspected - this GitHub Action is actually working as expected. The issue resides in lighthouse-check-status-action, which is a different repo altogether.

Let's keep this open here since the other repo isn't well known. I'm busy today and tomorrow, but should be able to get to the bottom of it on Friday.

@adamhenson
Copy link
Collaborator

@marklaatikainen thanks again for opening this issue. It has been resolved and released in foo-software/lighthouse-check-action@9.0.0.

We now "fast fail" a job when a runtime error occurs. Example

Closing this, but feel free to comment or re-open if needed.

@marklaatikainen
Copy link
Author

Thank you for quick fix 👍 Seems to be working now. @adamhenson

@adamhenson
Copy link
Collaborator

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants