Replies: 2 comments
-
Hey @jeffchew! I'd give 4.3.0 a try: https://github.com/percy/percy-storybook/releases/tag/v4.3.0 we cleaned up some things which should hopefully clear up these errors. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The problem
We have been having issues upgrading
@percy/storybook
from v3 to v4. We have made the suggestion of removing any ad service calls (by removing them entirely) but still seems to be an issue. The end result is that most snapshots go missing. This is observed in both our React components and Web Components versions of Storybook:PR opened:
carbon-design-system/carbon-for-ibm-dotcom#8128
React Percy latest result:
https://percy.io/538fc19a/Carbon-for-IBM.com-React/builds/18147514?utm_campaign=538fc19a&utm_content=Carbon-for-IBM.com-React&utm_source=github_status_public
Web Components Percy latest result:
https://percy.io/538fc19a/Carbon-for-IBM.com-Web-Components/builds/18148038?utm_campaign=538fc19a&utm_content=Carbon-for-IBM.com-Web-Components&utm_source=github_status_public
Environment
14
@percy/cli
version:1.2.0
4.2.0
Details
When digging into the logs, it appears that JS artifacts themselves (produced by Storybook) are getting blocked, an example of what we're seeing:
Debug logs
Attached:
Deploy Preview build log 20220517.txt
Code to reproduce issue
You can probably best see using the fork:
carbon-design-system/carbon-for-ibm-dotcom#8128
Steps to build:
yarn install
yarn build
cd packages/react
yarn build-storybook
yarn visual-snapshot
Beta Was this translation helpful? Give feedback.
All reactions