Logical folders allow for logical URI resolvers to collect items from different sources and concatenate the results. Currently only PATH:/// uses this feature. #4648
build.yaml
on: pull_request
test-linux
4m 56s
Matrix: tests
Annotations
7 errors and 6 warnings
|
test-linux
Task java.util.concurrent.FutureTask@477c404a[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@6414a71[Wrapped task = org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor@27ede61]] rejected from java.util.concurrent.ThreadPoolExecutor@7a6f4b89[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
|
|
tests (windows-latest)
Task java.util.concurrent.FutureTask@5ee1ad13[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@5419c663[Wrapped task = org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor@5ade3290]] rejected from java.util.concurrent.ThreadPoolExecutor@1be338ab[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]
|
|
tests (windows-latest)
Task java.util.concurrent.FutureTask@49e0e464[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@43188f14[Wrapped task = org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor@4ddf7907]] rejected from java.util.concurrent.ThreadPoolExecutor@ce2733c[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]
|
|
tests (windows-latest)
Task java.util.concurrent.FutureTask@47eb105d[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@4d137b2d[Wrapped task = org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor@43d48cff]] rejected from java.util.concurrent.ThreadPoolExecutor@2e986c4[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]
|
|
tests (windows-latest)
Task java.util.concurrent.FutureTask@321ee1b4[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@38e68ac4[Wrapped task = org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor@362173a8]] rejected from java.util.concurrent.ThreadPoolExecutor@771c7993[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
|
|
tests (windows-latest)
Task java.util.concurrent.FutureTask@6c99b981[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@6661d2f1[Wrapped task = org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor@68a6304d]] rejected from java.util.concurrent.ThreadPoolExecutor@299b3a76[Shutting down, pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
|
|
tests (windows-latest)
Task java.util.concurrent.FutureTask@7e3328f9[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@3f0e22c2[Wrapped task = org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor@3b31a1fb]] rejected from java.util.concurrent.ThreadPoolExecutor@1512826[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]
|
|
test-linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, codecov/codecov-action@v4, s4u/maven-settings-action@v3.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
tests (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, codecov/codecov-action@v4, s4u/maven-settings-action@v3.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
tests (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, codecov/codecov-action@v4, s4u/maven-settings-action@v3.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
builds
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, s4u/maven-settings-action@v3.1.0, SWAT-engineering/maven-full-artifacts-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
compiler-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, codecov/codecov-action@v4, s4u/maven-settings-action@v3.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
compiler-tests
Codecov:
Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
rascal-2156-1c6453a5ff8520b5a2452ba6bb01458013aa6baa
|
81.6 MB |
sha256:a43e1f419f5fc40379e3786e6a04a6e90d141957bf176c2b545230ff1f10855e
|
|