Experimental: Unified LSP server in rewatch #9733
nojafci.yml
on: pull_request
Matrix: build-compiler
test-devcontainer
20m 44s
api-docs
0s
Matrix: test-installation-npm
Matrix: test-installation-pnpm
Matrix: test-integration-rewatch
publish
0s
Annotations
15 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#L40
Error: no such table: types
❯ getTypeNames tests/lsp/db-sync-incremental.test.mjs:40:6
❯ tests/lsp/db-sync-incremental.test.mjs:131:19
❯ runLspTest helpers/test-context.mjs:763:5
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_SQLITE_ERROR', errcode: 1, errstr: 'SQL logic error' }
|
|
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:763: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:763: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#L85
AssertionError: expected [] to include 'greeting'
❯ tests/lsp/db-sync-incremental.test.mjs:85:22
❯ runLspTest helpers/test-context.mjs:763:5
|
|
tests/lsp/did-save.test.mjs > lsp didSave > publishes diagnostics for dependent files when a used API changes on save:
tests/rewatch_tests/tests/lsp/did-save.test.mjs#L277
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:277:5
|
|
tests/lsp/did-save.test.mjs > lsp didSave > publishes diagnostics for dependent files when a used API changes on save:
tests/rewatch_tests/tests/lsp/did-save.test.mjs#L277
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:277:5
|
|
tests/lsp/diagnostics.test.mjs > lsp diagnostics > publishes type error diagnostics for buffer content before initial build finishes:
tests/rewatch_tests/tests/lsp/diagnostics.test.mjs#L73
Error: Test timed out in 45000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/lsp/diagnostics.test.mjs:73:5
|
|
tests/lsp/diagnostics.test.mjs > lsp diagnostics > publishes type error diagnostics for buffer content before initial build finishes:
tests/rewatch_tests/tests/lsp/diagnostics.test.mjs#L73
Error: Test timed out in 45000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/lsp/diagnostics.test.mjs:73:5
|
|
tests/lsp/definition.test.mjs > lsp definition > jumps to definition of a module value:
tests/rewatch_tests/tests/lsp/definition.test.mjs#L6
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/definition.test.mjs:6:5
|
|
tests/lsp/definition.test.mjs > lsp definition > jumps to definition of a module value:
tests/rewatch_tests/tests/lsp/definition.test.mjs#L6
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/definition.test.mjs:6: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:763: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:763: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:763: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:763: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:42784e041c40d77d76ac1c2ac30607f6e69dbe7c1a7e65b31f70727cc181a896
|
|
|
binaries-darwin-x64
|
14.3 MB |
sha256:6d47482c4cd59d370110922049cca77999fc13c4a6a3a4edcfb44d7775d3e664
|
|
|
binaries-linux-x64
|
14 MB |
sha256:079b0501e5bc0609130ddc2313d56d5b3ebc86e02bb6809f6a59250d413d2ca0
|
|
|
lib-ocaml
|
5.44 MB |
sha256:88f2a6e170737e2bd6fb906342e9d4eaf107be44d143dd470abf9f19230a51fa
|
|