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
Is your feature request related to a problem? Please describe
Start-server-and-test is very reliable with storybook <= 5 because the HTTP endpoint isn't available until everything is built, but stop working with storybook 6 because the webserver is up before it is ready and shows a building n/m modules screen, therefore the endpoint test doesn't work anymore
Then in my CI, the timeout error happens a lot
TimeoutError: page.goto: Timeout 30000ms exceeded.
=========================== logs ===========================
navigating to "http://localhost:5002/iframe.html?id=taskfilterlist--story&viewMode=story", waiting until "domcontentloaded"
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.page.goto: Timeout 30000ms exceeded.
=========================== logs ===========================
navigating to "http://localhost:5002/iframe.html?id=taskfilterlist--story&viewMode=story", waiting until "domcontentloaded"
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.:
15 |
16 | const gotoStory = async (page: Page, id) => {
> 17 | await page.goto(http://${hostname}:5002/iframe.html?id=${id}&viewMode=story, {
| ^
18 | waitUntil: 'domcontentloaded',
19 | });
Describe the solution you'd like
A cli option to disable the progress screen
Describe alternatives you've considered
noo
Are you able to assist to bring the feature to reality?
no
Additional context
This ticket for Playwright was most likely caused by the same issue
The text was updated successfully, but these errors were encountered:
Either set navigation timeout to a very big number or run with a static build @ywongau how do you set a navigation timeout? (explanation or a link to the docs would be very helpfull )
Is your feature request related to a problem? Please describe
Start-server-and-test is very reliable with storybook <= 5 because the HTTP endpoint isn't available until everything is built, but stop working with storybook 6 because the webserver is up before it is ready and shows a
building n/m modules
screen, therefore the endpoint test doesn't work anymoreThen in my CI, the timeout error happens a lot
TimeoutError: page.goto: Timeout 30000ms exceeded.
=========================== logs ===========================
navigating to "http://localhost:5002/iframe.html?id=taskfilterlist--story&viewMode=story", waiting until "domcontentloaded"
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.page.goto: Timeout 30000ms exceeded.
=========================== logs ===========================
navigating to "http://localhost:5002/iframe.html?id=taskfilterlist--story&viewMode=story", waiting until "domcontentloaded"
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.:
15 |
16 | const gotoStory = async (page: Page, id) => {
> 17 | await page.goto(
http://${hostname}:5002/iframe.html?id=${id}&viewMode=story
, {| ^
18 | waitUntil: 'domcontentloaded',
19 | });
Describe the solution you'd like
A cli option to disable the progress screen
Describe alternatives you've considered
noo
Are you able to assist to bring the feature to reality?
no
Additional context
This ticket for Playwright was most likely caused by the same issue
The text was updated successfully, but these errors were encountered: