Skip to content

Fix Utils::json*() for native \JSON_THROW_ON_ERROR option #31

Fix Utils::json*() for native \JSON_THROW_ON_ERROR option

Fix Utils::json*() for native \JSON_THROW_ON_ERROR option #31

Triggered via push October 5, 2023 10:01
Status Failure
Total duration 1m 43s
Artifacts

ci.yml

on: push
Build lowest version
21s
Build lowest version
Matrix: Build on Windows
Matrix: Build
Fit to window
Zoom out
Zoom in

Annotations

48 errors and 17 warnings
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "RuntimeException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "RuntimeException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\ConnectException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\RequestException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\RequestException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\RequestException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\ConnectException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\RequestException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build lowest version
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.3, ^2.4.5)
The operation was canceled.
Build (8.0, ^1.9.1)
The operation was canceled.
Build (8.1, ^2.4.5)
The operation was canceled.
Build (8.0, ^2.4.5)
The operation was canceled.
Build (7.3, ^1.9.1)
The operation was canceled.
Build (7.4, ^1.9.1)
The operation was canceled.
Build (8.2, ^2.4.5)
The operation was canceled.
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "RuntimeException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "RuntimeException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^1.9.1)
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\RequestException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.4, ^2.4.5)
The operation was canceled.
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\ConnectException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "InvalidArgumentException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build on Windows (7.2)
Failed asserting that exception of type "Error" matches expected exception "GuzzleHttp\Exception\RequestException". Message was: "Undefined constant 'JSON_THROW_ON_ERROR'" at
Build (7.2, ^2.4.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build lowest version
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (7.3, ^2.4.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (8.0, ^1.9.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (8.1, ^2.4.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (8.0, ^2.4.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (7.3, ^1.9.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (7.4, ^1.9.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (8.2, ^2.4.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (7.2, ^1.9.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (7.4, ^2.4.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build on Windows (7.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build on Windows (8.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build on Windows (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build on Windows (8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build on Windows (7.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build on Windows (7.2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/