You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci(docs-infra): test_aio/test_aio_local jobs occasionally fail due to low PWA score #29910
By comparing the reports, the difference is that the SW is not detected in the failing runs (possibly due to it being registered after the app stabilizes).
Related Lighthouse issues: #2924, #5527, #6342
It turned out to be related to the old Chrome version used on CI (v70). Switching to puppeteer@1.14.0 (which brings in the equivalent of Chrome/75.0.3738.0), makes the tests pass reliably.
(Now we just need to figure out what is the best way to update Chrome across our CI jobs 😁)
It seems that the failurs are somehow related to the particular job instance/VM instance. For example, ssh'ing into a failing job/VM (e.g. #29921's 285524), will consistently fail the PWA tests. (Consistently, as in 50/50 failures.)
In that case, Lighthouse fails to detect the SW (and I indeed see from the server logs that the SW script was not requested). At the same time, loading the target URL in the same puppeteer instance, I can see the SW script being loaded and executing correctly (based on the server logs). For example:
// Open a browser.constbrowser=awaitpuppeteer.launch({defaultViewport: null,headless: false});constflags={port: newURL(browser.wsEndpoint()).port};// Open a page on the same browser to see if the SW is loaded.constpage=awaitbrowser.newPage();awaitpage.goto(url);awaitnewPromise(resolve=>setTimeout(resolve,10000));// SW is loaded :)awaitp.close();// Run Lighthouse.awaitlighthouse(url,flags,config);// SW is not loaded :(
(FWIW, I even tried removing node_modules/ (both in root and in aio/), re-running yarn --cwd=aio build and nothing changed 😞)
For completeness:
Ssh'ing into a passing job/VM (e.g. #29921's 285531) and running the PWA tests failed 2/15 times (i.e. still failed but with a much lower fewquency) 🤷♂️
Activity
ci(docs-infra): temporarily lower the min required PWA score for loca…
ci(docs-infra): temporarily lower the min required PWA score for loca…
ci(docs-infra): temporarily lower the min required PWA score for loca…
gkalpak commentedon Apr 16, 2019
By comparing the reports, the difference is that the SW is not detected in the failing runs (possibly due to it being registered after the app stabilizes).
Related Lighthouse issues: #2924, #5527, #6342
gkalpak commentedon Apr 16, 2019
It turned out to be related to the old Chrome version used on CI (v70). Switching to puppeteer@1.14.0 (which brings in the equivalent of
Chrome/75.0.3738.0), makes the tests pass reliably.(Now we just need to figure out what is the best way to update Chrome across our CI jobs 😁)
EDIT:
Here is a PoC of running the PWA score tests against the latest Chrome version (but we should have a more generic way - potentially based on puppeteer).
EDIT (2):
Actually, that doesn't seem to be entirely true: #29921 (comment) 😞
gkalpak commentedon Apr 16, 2019
Capturing some more info for future reference:
It seems that the failurs are somehow related to the particular job instance/VM instance. For example, ssh'ing into a failing job/VM (e.g. #29921's 285524), will consistently fail the PWA tests. (Consistently, as in 50/50 failures.)
In that case, Lighthouse fails to detect the SW (and I indeed see from the server logs that the SW script was not requested). At the same time, loading the target URL in the same puppeteer instance, I can see the SW script being loaded and executing correctly (based on the server logs). For example:
(FWIW, I even tried removing
node_modules/(both in root and inaio/), re-runningyarn --cwd=aio buildand nothing changed 😞)gkalpak commentedon Apr 16, 2019
For completeness:
Ssh'ing into a passing job/VM (e.g. #29921's 285531) and running the PWA tests failed 2/15 times (i.e. still failed but with a much lower fewquency) 🤷♂️
gkalpak commentedon Apr 17, 2019
We have a work-around (thx to GoogleChrome/lighthouse#5527 (comment)) 🎉
PR: #29953
ci(docs-infra): increase wait for SW on localhost to avoid CI flakes
ci(docs-infra): temporarily lower the min required PWA score for loca…
ci(docs-infra): increase wait for SW on localhost to avoid CI flakes (#…
ci(docs-infra): increase wait for SW on localhost to avoid CI flakes (a…
angular-automatic-lock-bot commentedon Sep 14, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.