We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, we currently experience an issue with sitespeed.io, which is using webpagetest-api to drive WPT: sitespeedio/sitespeed.io#1928
Unfortunately the error coming from webpagetest-api gives practically no context on where the error happened.
Could you maybe add a little more context to errors returned from webpagetest-api?
From what I can see it shouldn't be hard to add e.g. pathname to the err somehow here: https://github.com/marcelduran/webpagetest-api/blob/6bac270b59c44f1f4841231db14c16b8544e44ca/lib/webpagetest.js#L228
pathname
err
I'm not quite sure how the WPTAPIError is supposed to be used though and how I would integrated the new behavior into your test suite.
WPTAPIError
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, we currently experience an issue with sitespeed.io, which is using webpagetest-api to drive WPT:
sitespeedio/sitespeed.io#1928
Unfortunately the error coming from webpagetest-api gives practically no context on where the error happened.
Could you maybe add a little more context to errors returned from webpagetest-api?
From what I can see it shouldn't be hard to add e.g.
pathnameto theerrsomehow here:https://github.com/marcelduran/webpagetest-api/blob/6bac270b59c44f1f4841231db14c16b8544e44ca/lib/webpagetest.js#L228
I'm not quite sure how the
WPTAPIErroris supposed to be used though and how I would integrated the new behavior into your test suite.The text was updated successfully, but these errors were encountered: