Skip to content
CI

Add Object permissions to project and allow set add_check globally or per-project #692

Sign in to view logs

Add Object permissions to project and allow set add_check globally or per-project

Add Object permissions to project and allow set add_check globally or per-project #692

Triggered via pull request June 7, 2026 15:48
@mchehabmchehab
opened #653
mchehab:object-permissions
Status Failure
Total duration 3m 40s
Artifacts –

ci.yaml

on: pull_request
Run linters
2m 23s
Run linters
Build docs
3s
Build docs
Matrix: Docker Image tests
Matrix: Run unit tests
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 7 warnings
Docker Image tests (postgres)
Process completed with exit code 1.
Run unit tests (3.10, postgres)
Process completed with exit code 1.
Run unit tests (3.10, mysql)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.10, sqlite3)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.11, postgres)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.11, mysql)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.13, mysql)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.9, postgres)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.12, postgres)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.11, sqlite3)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.9, sqlite3)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.12, sqlite3)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.9, mysql)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.13, sqlite3)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.12, mysql)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.12, mysql)
The operation was canceled.
Run unit tests (3.13, postgres)
The strategy configuration was canceled because "test._3_10_postgres" failed
Run unit tests (3.13, postgres)
The operation was canceled.
Build docs
This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v3`. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
Docker Image tests (mysql)
The strategy configuration was canceled because "docker-compose.postgres" failed
Docker Image tests (mysql)
The operation was canceled.
Docker Image tests (sqlite3)
The strategy configuration was canceled because "docker-compose.postgres" failed
Docker Image tests (sqlite3)
The operation was canceled.
Run linters
Process completed with exit code 1.
Docker Image tests (postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Run unit tests (3.10, postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Run unit tests (3.13, postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Docker Image tests (mysql)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Docker Image tests (sqlite3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Run linters
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v4, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Run linters
Restore cache failed: Dependencies file is not found in /home/runner/work/patchwork/patchwork. Supported file pattern: go.sum