Skip to content
Tests

[stable31] fix: correct env var parsing when there is only one entry #1948

Sign in to view logs

[stable31] fix: correct env var parsing when there is only one entry

[stable31] fix: correct env var parsing when there is only one entry #1948

Triggered via pull request February 12, 2025 06:24
@backportbotbackportbot[bot]
opened #509
backport/508/stable31
Status Failure
Total duration 24m 16s
Artifacts 4

tests.yml

on: pull_request
NC_Py_API • PgSQL
3m 32s
NC_Py_API • PgSQL
NC_Py_API • MySQL
4m 25s
NC_Py_API • MySQL
NC_Py_API • Oracle
10m 58s
NC_Py_API • Oracle
APCu • NC_Py_API • MySQL
3m 40s
APCu • NC_Py_API • MySQL
Tests-OK
0s
Tests-OK
Fit to window
Zoom out
Zoom in

Annotations

2 errors
NC_Py_API • MySQL
Process completed with exit code 1.
NC_Py_API • Oracle
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size Digest
apcu_mysql_nc_py_api_nextcloud.log Expired
3.87 KB
sha256:3e6fd4bff5e7b4ef440ba4363cfff63cf3e0b0e26376e17df5b4001fa62ce096
mysql_nc_py_api_nextcloud.log Expired
5.04 KB
sha256:f5bfdff6c20075e03981f837198c53cf04e0fa7c1b7497de6461d9004546b5a0
oci_nc_py_api_nextcloud.log Expired
4.79 KB
sha256:1fd11a4425305e727a2f1fada2046a4eeef64110ea962be36814a5a4aaa45bfb
pgsql_nc_py_api_nextcloud.log Expired
3.76 KB
sha256:587dc31b14af4be92729df59beeb75bf1fb7560334ed0cdba9eab0bba6bdce25