Bai 1111 allow semver matching and latest semver for releases #4715
build.js.yml
on: pull_request
unit_testing
2m 50s
style
1m 41s
kubernetes
9m 24s
end_to_end
6m 16s
integration_python
5m 49s
Annotations
2 errors
Unhandled error:
backend/src/utils/error.ts#L8
Bailo Error: BAILO configuration error: Could not configure or initialise Clam AV
❯ GenericError src/utils/error.ts:8:15
❯ Module.ConfigurationError src/utils/error.ts:56:10
❯ src/connectors/fileScanning/index.ts:28:17
❯ processTicksAndRejections node:internal/process/task_queues:95:5
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 503, context: undefined, logger: undefined }
This error originated in "test/services/smtp/smtp.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "test/services/smtp/smtp.spec.ts". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
unit_testing
Process completed with exit code 1.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
bailo_backend
|
94.7 MB |
|
bailo_frontend
|
140 MB |
|
logs
|
40.9 KB |
|
python-logs
|
31.5 KB |
|