Skip to content

test: add integration tests for multi-backend configs, agent events, … #61

test: add integration tests for multi-backend configs, agent events, …

test: add integration tests for multi-backend configs, agent events, … #61

Triggered via push March 21, 2026 11:35
Status Failure
Total duration 1m 18s
Artifacts

ci.yml

on: push
Integration Tests
Integration Tests
E2E Tests
E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 3 warnings
Code Quality
Process completed with exit code 1.
Security Audit
Process completed with exit code 1.
Unit Tests: test/zentinel_cp_web/controllers/api/internal_ca_controller_test.exs#L87
test GET /api/v1/projects/:project_slug/internal-ca/ca.pem downloads CA certificate (ZentinelCpWeb.Api.InternalCaControllerTest)
Unit Tests: test/zentinel_cp_web/controllers/api/internal_ca_controller_test.exs#L50
test POST /api/v1/projects/:project_slug/internal-ca returns 422 when CA already exists (ZentinelCpWeb.Api.InternalCaControllerTest)
Unit Tests: test/zentinel_cp_web/controllers/api/internal_ca_controller_test.exs#L169
test GET /api/v1/projects/:project_slug/internal-ca/certificates/:id returns 404 for nonexistent certificate (ZentinelCpWeb.Api.InternalCaControllerTest)
Unit Tests: test/zentinel_cp/services/ca_crypto_test.exs#L113
test issue_client_certificate/5 issues certificate with RSA CA (ZentinelCp.Services.CACryptoTest)
Unit Tests: test/zentinel_cp/services/ca_crypto_test.exs#L51
test generate_ca_certificate/3 generates a valid CA certificate with RSA key (ZentinelCp.Services.CACryptoTest)
Unit Tests: test/zentinel_cp/services/ca_crypto_test.exs#L65
test issue_client_certificate/5 issues a certificate signed by the CA (ZentinelCp.Services.CACryptoTest)
Unit Tests: test/zentinel_cp/services/ca_crypto_test.exs#L140
test generate_crl/3 generates an empty CRL (ZentinelCp.Services.CACryptoTest)
Unit Tests: test/zentinel_cp/services/ca_crypto_test.exs#L126
test generate_crl/3 generates a CRL with revoked entries (ZentinelCp.Services.CACryptoTest)
Unit Tests: test/zentinel_cp/services/ca_crypto_test.exs#L94
test issue_client_certificate/5 issues certificate with OU (ZentinelCp.Services.CACryptoTest)
Unit Tests: test/zentinel_cp/services/ca_crypto_test.exs#L26
test generate_ca_certificate/3 generates a valid self-signed CA certificate with EC key (ZentinelCp.Services.CACryptoTest)
Code Quality
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. 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/
Security Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. 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/
Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. 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/