Skip to content
CI

Experimental: Unified LSP server in rewatch #9734

Sign in to view logs

Experimental: Unified LSP server in rewatch

Experimental: Unified LSP server in rewatch #9734

Triggered via pull request March 19, 2026 12:34
@nojafnojaf
synchronize #8243
nojaf:rewatch-lsp
Status Failure
Total duration 24m 17s
Artifacts 4

ci.yml

on: pull_request
Matrix: build-compiler
test-devcontainer
19m 24s
test-devcontainer
pkg-pr-new
0s
pkg-pr-new
api-docs
0s
api-docs
Matrix: test-installation-npm
Matrix: test-installation-pnpm
Matrix: test-integration-rewatch
publish
0s
publish
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 4 warnings
build-compiler (ubuntu-24.04-arm, ocaml-variants.5.3.0+options,ocaml-option-static, true, true, t...
Process completed with exit code 1.
tests/lsp/db-sync-incremental.test.mjs > lsp incremental db sync > updates module types in rescript.db after a file is saved: tests/rewatch_tests/tests/lsp/db-sync-incremental.test.mjs#L132
AssertionError: expected [] to include 'user' ❯ tests/lsp/db-sync-incremental.test.mjs:132:21 ❯ runLspTest helpers/test-context.mjs:764:5
tests/lsp/db-sync-incremental.test.mjs > lsp incremental db sync > updates module types in rescript.db after a file is saved: tests/rewatch_tests/tests/lsp/db-sync-incremental.test.mjs#L132
AssertionError: expected [] to include 'user' ❯ tests/lsp/db-sync-incremental.test.mjs:132:21 ❯ runLspTest helpers/test-context.mjs:764:5
build-compiler (windows-2025, 5.3.0, true, win32-x64, x86_64-pc-windows-gnu, .exe)
Process completed with exit code 1.
tests/lsp/initial-build.test.mjs > lsp > builds project with lsp profile artifacts on initial build: tests/rewatch_tests/tests/lsp/initial-build.test.mjs#L95
Error: Test timed out in 60000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/lsp/initial-build.test.mjs:95:5
tests/lsp/initial-build.test.mjs > lsp > builds project with lsp profile artifacts on initial build: tests/rewatch_tests/tests/lsp/initial-build.test.mjs#L95
Error: Test timed out in 60000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/lsp/initial-build.test.mjs:95:5
tests/lsp/did-save.test.mjs > lsp didSave > produces JS when another package has errors: tests/rewatch_tests/tests/lsp/did-save.test.mjs#L246
Error: Test timed out in 60000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/lsp/did-save.test.mjs:246:5
tests/lsp/did-save.test.mjs > lsp didSave > produces JS when another package has errors: tests/rewatch_tests/tests/lsp/did-save.test.mjs#L246
Error: Test timed out in 60000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/lsp/did-save.test.mjs:246:5
tests/lsp/db-sync-incremental.test.mjs > lsp incremental db sync > updates module types in rescript.db after a file is saved: tests/rewatch_tests/tests/lsp/db-sync-incremental.test.mjs#L127
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ tests/lsp/db-sync-incremental.test.mjs:127:33 ❯ runLspTest helpers/test-context.mjs:764:5
tests/lsp/db-sync-incremental.test.mjs > lsp incremental db sync > updates module types in rescript.db after a file is saved: tests/rewatch_tests/tests/lsp/db-sync-incremental.test.mjs#L127
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ tests/lsp/db-sync-incremental.test.mjs:127:33 ❯ runLspTest helpers/test-context.mjs:764:5
tests/lsp/db-sync-incremental.test.mjs > lsp incremental db sync > updates module values in rescript.db after a file is saved: tests/rewatch_tests/tests/lsp/db-sync-incremental.test.mjs#L79
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ tests/lsp/db-sync-incremental.test.mjs:79:33 ❯ runLspTest helpers/test-context.mjs:764:5
tests/lsp/db-sync-incremental.test.mjs > lsp incremental db sync > updates module values in rescript.db after a file is saved: tests/rewatch_tests/tests/lsp/db-sync-incremental.test.mjs#L79
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ tests/lsp/db-sync-incremental.test.mjs:79:33 ❯ runLspTest helpers/test-context.mjs:764:5
build-compiler (ubuntu-24.04-arm, ocaml-variants.5.3.0+options,ocaml-option-static, true, true, t...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-compiler (ubuntu-24.04, ocaml-variants.5.0.0+options,ocaml-option-static, linux-x64, x86_64...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-compiler (ubuntu-24.04, ocaml-variants.5.3.0+options,ocaml-option-static, true, true, linux...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test-devcontainer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@v0.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
binaries-darwin-arm64
15.6 MB
sha256:d7e024c47dcca6e306f12bd4305c100997d3954370f017950b2e4e0f57826b7d
binaries-darwin-x64
14.3 MB
sha256:7d481d6314bcec9ff30a6d3f03363c4dbcb4a13bdfde726f5fd4c8495c8c43a3
binaries-linux-x64
14 MB
sha256:20e8bf9ffeb81a65f5ebb46a0b43cb344129292fb1c917fec141ba24956d6963
lib-ocaml
5.44 MB
sha256:727f287ff54e21b12c0b864657e7f6455b184592e608b708f9d4de3de133a3c9