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

fix: add more helpful error message when fMP is missing #1959

Merged
merged 1 commit into from
Apr 4, 2017

Conversation

patrickhulce
Copy link
Collaborator

@patrickhulce patrickhulce commented Apr 3, 2017

filed #1960 to track the issue itself

@addyosmani
Copy link
Member

👍 Better than what we had here before.

I do wonder with failures like this as a whole whether we should be more proactive in telling users to re-run Lighthouse vs considering it a fail state they can't recover from.

@brendankenny
Copy link
Member

brendankenny commented Apr 3, 2017

I do wonder with failures like this as a whole whether we should be more proactive in telling users to re-run Lighthouse vs considering it a fail state they can't recover from.

yeah, we already see this in plots, where we should add plotting of the error rate as one of our metrics, but should also probably discard those runs to get full samples

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while looking at closure stuff I've also run into this with FMP. Nice to have more assertions rather than passing around undefineds

@brendankenny brendankenny merged commit 0bf1744 into master Apr 4, 2017
@brendankenny brendankenny deleted the borked_trace_error_msg branch April 4, 2017 00:04
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.

None yet

3 participants