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
Hi team, thanks for your great efforts for building and maintaining this amazing library for years!
Currently one of our product is using test runner to run interaction tests locally. However, after my local machine os upgraded to 15.x, the test runner no longer working. The reason why im sure is about the os version because i verified both both CI and machine + older os version, they both work well.
There are a few things abnormal i noticed in my local
npx storybook -build takes crazy cpu consumption. Im using M2 chip but it might take 600%+ when running this command.( normally just 100%-200%
error message returned when im running the test:
This error seems generated from the src/setup-page-scripts.ts, does this meaning that the build is actually not considered as successful?(but the stoybook dev server looks quite ok in my local machine
Hey there @HJZzzzz I haven't seen any report about this anywhere else, it's quite odd.
The error message is shown when a story test fails when the test-runner visits it, so it didn't have to do with storybook build, but rather how the story rendered when it was accessed.
I'd really recommend you to upgrade your packages, they are quite outdated, please run npx storybook@latest upgrade, try it out and report back in case things are still not ok! Thanks 🙏
Describe the bug
Hi team, thanks for your great efforts for building and maintaining this amazing library for years!
Currently one of our product is using test runner to run interaction tests locally. However, after my local machine os upgraded to 15.x, the test runner no longer working. The reason why im sure is about the os version because i verified both both CI and machine + older os version, they both work well.
There are a few things abnormal i noticed in my local
npx storybook -build
takes crazy cpu consumption. Im using M2 chip but it might take 600%+ when running this command.( normally just 100%-200%To Reproduce
System
Additional context
No response
The text was updated successfully, but these errors were encountered: