ci with github actions fails on plain fork
gberche-orange opened this issue · comments
Description
Our team is trying to contribute to feature #1051
The github action on our fork such as https://github.com/orange-cloudfoundry/hedgedoc/actions/runs/7628501815/job/20780214477 are failing with
Run yarn build
• Packages in scope: @hedgedoc/backend, @hedgedoc/commons, @hedgedoc/dev-reverse-proxy, @hedgedoc/docs, @hedgedoc/frontend, @hedgedoc/html-to-react, @hedgedoc/markdown-it-plugins
• Running build in 7 packages
• Remote caching enabled
Oops! Turbo has crashed.A report has been written to /tmp/report-f6366f85-5fd6-4915-b46d-ada007a3c180.toml
Please open an issue at https://github.com/vercel/turbo/issues/new/choose and include this file
Oops! Turbo has crashed.
We tried signing up into https://vercel.com/signup, creating a new token into https://vercel.com/account/tokens and defining a gitub secret TURBO_TOKEN but this is insufficient to fix the issue
I notice that the build expects as well a TURBO_TEAM as whell as a TURBO_API, but failed so far to find how to get the TURBO_API value
hedgedoc/.github/workflows/test-and-build.yml
Lines 47 to 49 in 01d7eb9
https://turbo.build/repo/docs/ci/github-actions provides guidelines for TURBO_TEAM but not yet TURBO_API variable
https://turbo.build/repo/docs/reference/command-line-reference/link mentions
--api
type: string
Defaults to https://api.vercel.com
What would be the required steps to get a CI running to contribute new features ?
Thanks in advance
Steps to reproduce
enable github actions
Expected behaviour
ci works
Logs
No response
Config
No response
Your Setup
- Host OS: [e.g. Ubuntu 20.04]
- NodeJS version: [run
node --version] - HedgeDoc version: (Click "Releases" in the footer)
Additional context
No response
After setting TURBO_TOKEN, TURBO_TEAM and TURBO_API, the CI now fails at https://github.com/orange-cloudfoundry/hedgedoc/actions/runs/7629432489/job/20782829479 with
After setting TURBO_TOKEN, TURBO_TEAM and TURBO_API, the CI now fails at https://github.com/orange-cloudfoundry/hedgedoc/actions/runs/7629432489/job/20782829479 with
\#15 13.27 @hedgedoc/commons:build: ../node_modules/@jest/environment/node_modules/@types/node/assert.d.ts(991,14): error TS2300: Duplicate identifier 'assert'. [...] \#15 13.28 @hedgedoc/commons:build: ../node_modules/@jest/environment/node_modules/@types/node/os.d.ts(249,19): error TS2649: Cannot augment module 'signals' with value exports because it resolves to a non-module entity. [...] \#15 13.38 @hedgedoc/commons:build: ERROR: command finished with error: command (/usr/src/app/commons) /tmp/xfs-98c8944c/yarn run build exited (2) \#15 13.44 @hedgedoc/html-to-react:build: ERROR: command finished with error: command (/usr/src/app/html-to-react) /tmp/xfs-98c8944c/yarn run build exited (129) \#15 13.44 @hedgedoc/commons#build: command (/usr/src/app/commons) /tmp/xfs-98c8944c/yarn run build exited (2) \#15 13.44 @hedgedoc/html-to-react#build: command (/usr/src/app/html-to-react) /tmp/xfs-98c8944c/yarn run build exited (129) \ \#15 13.45 \#15 13.45 Tasks: 1 successful, 3 total \#15 13.45 Cached: 0 cached, 3 total \#15 13.45 Time: 11.644s \#15 13.45 Failed: @hedgedoc/commons#build, @hedgedoc/html-to-react#build \#15 13.45 \#15 13.45 ERROR run failed: command exited (129) \#15 ERROR: process "/bin/sh -c yarn build --filter=frontend --no-cache --no-daemon" did not complete successfully: exit code: 129 ------ > [builder 5/5] RUN yarn build --filter=frontend --no-cache --no-daemon: 13.44 @hedgedoc/html-to-react:build: ERROR: command finished with error: command (/usr/src/app/html-to-react) /tmp/xfs-98c8944c/yarn run build exited (129) 13.44 @hedgedoc/commons#build: command (/usr/src/app/commons) /tmp/xfs-98c8944c/yarn run build exited (2) 13.44 @hedgedoc/html-to-react#build: command (/usr/src/app/html-to-react) /tmp/xfs-98c8944c/yarn run build exited (129) 13.45 13.45 Tasks: 1 successful, 3 total 13.45 Cached: 0 cached, 3 total 13.45 Time: 11.644s 13.45 Failed: @hedgedoc/commons#build, @hedgedoc/html-to-react#build 13.45 13.45 ERROR run failed: command exited (129) ------ Dockerfile:29 -------------------- 27 | ARG TURBO_TOKEN 28 | 29 | >>> RUN yarn build --filter=frontend --no-cache --no-daemon 30 | 31 | # RUNNER -------------------- ERROR: failed to solve: process "/bin/sh -c yarn build --filter=frontend --no-cache --no-daemon" did not complete successfully: exit code: 129 Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c yarn build --filter=frontend --no-cache --no-daemon" did not complete successfully: exit code: 129
Usually it's not necessary to define the API-URL. We do it anyway because we're not using vercels cache but a self hosted alternative. So for it to work you probably have to set TURBO_API to https://api.vercel.com.
I tried to compile the project from scratch without cache and run into a similar error. I hope that #5400 will fix this.
great, thanks @mrdrogdrog for your response and fix. We'll update/close this issue as we pull #5400
It's merged. Try refreshing your develop branch
Thanks, apparently #5400 or one of the following commits fixed the build as https://github.com/orange-cloudfoundry/hedgedoc/actions/runs/7641126391/job/20817743359 passed, tested by @Guilamb
https://github.com/orange-cloudfoundry/hedgedoc/commits/develop/
