chore: bump @mongosh dependencies
#2070
kmruizcode_health.yaml
on: pull_request
Matrix: Run MongoDB tests
Run Atlas tests
2m 26s
Report Coverage
47s
Annotations
10 errors, 9 warnings, and 1 notice
|
Run MongoDB tests (macos-latest)
Process completed with exit code 1.
|
|
tests/integration/tools/mongodb/connect/connect.test.ts > Connect tool > with invalid connection string > returns error message:
tests/integration/tools/mongodb/connect/connect.test.ts#L131
AssertionError: expected 'You need to connect to a MongoDB inst…' to contain 'The configured connection string is n…'
- Expected
+ Received
- The configured connection string is not valid.
+ You need to connect to a MongoDB instance before you can access its data.
+ Please use one of the following tools: "connect" to connect to a MongoDB instance or update the MCP server configuration to include a connection string. Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.
❯ tests/integration/tools/mongodb/connect/connect.test.ts:131:33
|
|
tests/integration/tools/mongodb/connect/connect.test.ts > SwitchConnection tool > when the arugment connection string is invalid > returns error message:
tests/integration/tools/mongodb/connect/connect.test.ts#L81
AssertionError: expected 'You need to connect to a MongoDB inst…' to contain 'The configured connection string is n…'
- Expected
+ Received
- The configured connection string is not valid.
+ You need to connect to a MongoDB instance before you can access its data.
+ Please use one of the following tools: "connect" to connect to a MongoDB instance or update the MCP server configuration to include a connection string. Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.
❯ tests/integration/tools/mongodb/connect/connect.test.ts:81:33
|
|
Run MongoDB tests (ubuntu-latest)
Process completed with exit code 1.
|
|
tests/integration/tools/mongodb/connect/connect.test.ts > Connect tool > with invalid connection string > returns error message:
tests/integration/tools/mongodb/connect/connect.test.ts#L131
AssertionError: expected 'You need to connect to a MongoDB inst…' to contain 'The configured connection string is n…'
- Expected
+ Received
- The configured connection string is not valid.
+ You need to connect to a MongoDB instance before you can access its data.
+ Please use one of the following tools: "connect" to connect to a MongoDB instance or update the MCP server configuration to include a connection string. Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.
❯ tests/integration/tools/mongodb/connect/connect.test.ts:131:33
|
|
tests/integration/tools/mongodb/connect/connect.test.ts > SwitchConnection tool > when the arugment connection string is invalid > returns error message:
tests/integration/tools/mongodb/connect/connect.test.ts#L81
AssertionError: expected 'You need to connect to a MongoDB inst…' to contain 'The configured connection string is n…'
- Expected
+ Received
- The configured connection string is not valid.
+ You need to connect to a MongoDB instance before you can access its data.
+ Please use one of the following tools: "connect" to connect to a MongoDB instance or update the MCP server configuration to include a connection string. Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.
❯ tests/integration/tools/mongodb/connect/connect.test.ts:81:33
|
|
Run MongoDB tests (windows-latest)
Process completed with exit code 1.
|
|
tests/integration/tools/mongodb/connect/connect.test.ts > Connect tool > with invalid connection string > returns error message:
tests/integration/tools/mongodb/connect/connect.test.ts#L131
AssertionError: expected 'You need to connect to a MongoDB inst…' to contain 'The configured connection string is n…'
- Expected
+ Received
- The configured connection string is not valid.
+ You need to connect to a MongoDB instance before you can access its data.
+ Please use one of the following tools: "connect" to connect to a MongoDB instance or update the MCP server configuration to include a connection string. Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.
❯ tests/integration/tools/mongodb/connect/connect.test.ts:131:33
|
|
tests/integration/tools/mongodb/connect/connect.test.ts > SwitchConnection tool > when the arugment connection string is invalid > returns error message:
tests/integration/tools/mongodb/connect/connect.test.ts#L81
AssertionError: expected 'You need to connect to a MongoDB inst…' to contain 'The configured connection string is n…'
- Expected
+ Received
- The configured connection string is not valid.
+ You need to connect to a MongoDB instance before you can access its data.
+ Please use one of the following tools: "connect" to connect to a MongoDB instance or update the MCP server configuration to include a connection string. Note to LLM: do not invent connection strings and explicitly ask the user to provide one. If they have previously connected to MongoDB using MCP, you can ask them if they want to reconnect using the same connection string.
❯ tests/integration/tools/mongodb/connect/connect.test.ts:81:33
|
|
Report Coverage
Unable to download artifact(s): Artifact not found for name: test-results
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
|
Run MongoDB tests (ubuntu-latest)
No files were found with the provided path: coverage/lcov.info. No artifacts will be uploaded.
|
|
Run MongoDB tests (ubuntu-latest)
1 added, 0 removed; done.
|
|
Run MongoDB tests (ubuntu-latest)
rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
|
|
Run MongoDB tests (ubuntu-latest)
Updating certificates in /etc/ssl/certs...
|
|
Run MongoDB tests (ubuntu-latest)
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
|
|
Run Atlas tests
1 added, 0 removed; done.
|
|
Run Atlas tests
rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
|
|
Run Atlas tests
Updating certificates in /etc/ssl/certs...
|
|
Run Atlas tests
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
|
|
Run MongoDB tests (windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
atlas-test-results
|
16.4 KB |
sha256:9836a6856fc3d15a934aea092beb4cdbaac6b03479f2b100e99dc4603977776d
|
|
|
run-atlas-tests-permissions-19de2152fa739298eac820eaf8abaece
|
140 Bytes |
sha256:de8bb3a6cf3cd615014110b075c58d260995b4b74c9df1fc953d7c53cdd858b2
|
|
|
run-tests-permissions-9a7914f6dc06141d3f4403e5163bc4aa
|
140 Bytes |
sha256:8d4087b13774b0c93a7cac8b685ed62a38526dc4d239aca8c9dfc00237dad4f1
|
|