New issue
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
building your Storybook fails (only with chromatic) #227
Comments
Hi @thelfensdrfer did you figure this out? Perhaps you could write into Chromatic support about this, this repo isn't the best place for quick turnarounds ;) |
No, I did not. |
Why is this closed? |
@nikandlv if you are seeing the issue, can you write into Chromatic support? These issues tend to be customer specific and involve private details of their CI setup so a public repo isn't an appropriate place to discuss them. |
This does not make sense at all. Which parts of this issue are confidential? Edit: My project is somewhat open source and I am willing to share any needed details. If you do not want to work with public issues, that's fine. But please deactivate issues then. Otherwise it just looks like this is a great project without any issues, which it is not, a project of without issues I mean. It is still great 👍 |
@thelfensdrfer I mean specifically issues with your Storybook failing to build on CI, when triggered by Chromatic. In my experience it is a fairly common problem that users have but it is rarely a bug in the The reason I would prefer you to write into support is I want you to get your issue resolved so you can get started with Chromatic, and our support is both synchronous and has regular rotation of folks watching it; unlike these issues which are looked at more infrequently! I wouldn't close an issue for something more specific as evidenced by the fact that we have 16 open issues! |
This is true. I just hate private issue tracking because maybe some other guy or gal has the same problem I have. Maybe it will turn out the problems are different, but maybe they aren't.
In this case CI isn't the problem. The initial command above was executed in a default bash terminal on my development machine. If chromatic would just call chromatic-cli/bin/tasks/build.js Lines 46 to 69 in 7710e62
But there is in fact not much going on there, so I can't say where the problem is at the moment. |
@nikandlv I solved this issue by building the storybook manually and only upload it via the chromatic-cli: yarn build-storybook
npx chromatic --exit-zero-on-changes -d storybook-static/ |
I have been having the same issue from my local machine as well. I have even tried previous branches which worked just fine. Chromatic had been working as of 1/20/2021. Then we had removed the step from our CI for a bit. When we added it back in about a week ago, the "Building Your Storybook" step just hangs and does not move forward. I can run |
@divijb did your version of SB change in the meantime? Can you run |
Neither the Chromatic or the SB versions changed. In fact, I tried an older branch with the same results. This was failing on CI, so I have been trying to figure it out locally, without any luck. I've resorted to doing what @thelfensdrfer is doing, building out storybook and then just uploading |
^ To be clear, I inherited this and it was working on CI just fine for a couple of months, until late January. This week was the first time I've been trying it locally and it was failing at the |
Does that mean it isn't failing locally? Using a separate |
I have the same problem for a while. I can build the storybook manually running error log
IMHO this error message doesn't help or make sense sin my build-storybook cli is working properly. I wonder if downgrade will solve this problem, since it was working properly before. |
@inaki what version of npm/yarn are you using? that is a strange error indeed. Maybe worth a separate issue. |
I was using this versions 💀 : node: v14.15.1 I switch and use these now and is working 👍 : node: v13.14.0 Thanks @tmeasday :) |
The Chromatic |
When it fails locally does it just hang? |
It seems to hang for a long period. Much much longer than it should take to show fail/success of storybook build process. It eventually shows that it failed. |
Same. |
@divijb @thelfensdrfer and what does it say when it fails? Is there something in the log? |
|
Oh, sorry I missed the fact that the |
Encountered the same issue when run
|
Seeing a similar issue on my project (https://github.com/lab49/react-value-flash), but without any error output. I'm building on CircleCI. The task times out after 10 minutes, and I see the following output: > @lab49/react-value-flash@0.1.3 chromatic
> npx chromatic --project-token <censored> "--exit-zero-on-changes"
Chromatic CLI v5.1.0
https://www.chromatic.com/docs/cli
Authenticating with Chromatic
→ Connecting to https://index.chromatic.com
Authenticated with Chromatic
→ Using project token '******qeah'
Retrieving git information
Retrieved git information
→ Commit '4815d36' on branch 'master'; found 1 baseline commit
Collecting Storybook metadata
Collected Storybook metadata
→ Storybook v6.0.16 for React; supported addons found: Actions, Backgrounds, Docs, Viewport
Building your Storybook
→ Running command: build-storybook -- --output-dir /tmp/chromatic-25184kHIdxmQ2NVO
Too long with no output (exceeded 10m0s): context deadline exceeded |
Had the same issue and it was resolved by changing my package.json script from |
For me this issue was temporarily fixed by changing my npm version to |
This also worked out for me, thanks for that bro! I'm using chromatic@5.6.2, npm@7.7.6 and node v15.12.0 |
Worked for me. Thank you! |
The issue where the "build storybook" step hangs until it times out was traced back to the use of If you still encounter this after upgrading, please report/reopen. In case you cannot upgrade to the latest CLI, the workaround is to use |
Hi guys i'm having error when building storybook , yarn version is v1.22.4 and node version is v14.6.0 Anyone have any idea how i can solve this?
|
Hi! A couple of questions. First, did you try following the directions in that error, particularly the bolded one?
Second, if those directions don't address your problem, it's probably better to open a new issue rather than comment on this closed one, unless you're confident that your issue is caused by the fix detailed here not actually working. |
Hi Guys, I'm trying to run Chromatic on premises outside the Git referring the document - How to continue setup if you require SSO, on-premises, or have a different Git provider. But when running the project token command, getting below error: Chromatic CLI v6.5.1 √ Authenticated with Chromatic × Failed to retrieve git information If you need help, please chat with us at https://www.chromatic.com/docs/cli for the fastest response. Please provide us with the above CLI output and the following info: Any idea what I'm not able to proceed with a separate chromatic account ? |
@akhilgopalv14 — That issue is unrelated to this one, and is best resolved by chatting with us via the link in that error message. That said, I'm not sure Chromatic can be run on-premises, as it needs access to your project's git history to properly take snapshots and calculate baselines. |
I had this issue and was able to resolve it by deleting all of my empty assets folders and their corresponding references in DetailsAngular I didn't receive any errors when building Storybook outside of the Github workflow, so I isolated the storybook build in the Github workflow and that yielded more descriptive errors, which allowed me to correct them. Build error fixesThe Storybook build threw an error for all of my assets folders that were empty. I deleted those folders and removed their references from Working ymlI don't know why the Storybook build behavior is different in the Github action. After resolving the errors I was able to remove the isolated Storybook build Here is my working workflow file: name: 'Chromatic Dev'
on:
push:
branches:
- dev
defaults:
run:
working-directory: buoy-workspace
jobs:
chromatic-deployment:
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3
with:
fetch-depth: 0
- name: Install dependencies and build
run: |
npm ci
npm run build-buoy
- name: Publish to Chromatic
uses: chromaui/action@v1
with:
workingDir: buoy-workspace
projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
exitZeroOnChanges: true |
Had the same issue, but it was caused by that I was missing a script inside my package.json that was specifically named "build-storybook", that chromatic then failed to run. We're using Nx, with our own npm scripts, so we apparently didn't have the exact Storybook setup that the software has been designed for. Managed to solve it by following the advice above, namely to run
Had the same issue, caused by that a script for building Storybook called "build-storybook" wasn't present. Managed to get past it by using the command suggested in the quoted comment. Then adding a script with the explicit name in that branch's pull request |
yarn: 1.22.5
npm: 6.14.9
build-storybook.log
exists but is empty. If I run the failed commandnpm run --silent build-storybook -- --output-dir /tmp/chromatic--31522-Y2kKkIx9HmLt
manually, the storybook gets build.┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: