CLI | Сборка и тестирование #170
Bayselonarrendcli_test.yml
on: workflow_dispatch
Testing-twitter
6s
Testing-notion
9s
Testing-yandex
8s
Testing-yadisk
10s
Testing-google
4s
Testing-gcalendar
11s
Testing-gdrive
7s
Clear-Cache
2s
Annotations
172 errors and 22 warnings
|
Testing-google
Process completed with exit code 126.
|
|
Testing-google
Process completed with exit code 126.
|
|
Testing-google
Process completed with exit code 126.
|
|
Testing-google
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
Process completed with exit code 126.
|
|
Testing-twitter
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-gdrive
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-notion
Process completed with exit code 126.
|
|
Testing-yandex
Process completed with exit code 126.
|
|
Testing-yandex
Process completed with exit code 126.
|
|
Testing-yandex
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-yandex
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-gcalendar
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-yadisk
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-viber
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-telegram
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
ENOENT: no such file or directory, open '/home/runner/work/OpenIntegrations/OpenIntegrations/data.json'
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Testing-vk
Process completed with exit code 126.
|
|
Decode
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/save@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: otymko/[email protected], actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-google
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-google
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-twitter
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-twitter
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-gdrive
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-gdrive
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-notion
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-notion
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-yandex
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-yandex
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-gcalendar
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-gcalendar
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-yadisk
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-yadisk
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-viber
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-viber
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-telegram
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-telegram
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Testing-vk
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache/restore@v3, rgarcia-phi/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Testing-vk
The following actions uses node12 which is deprecated and will be forced to run on node16: rgarcia-phi/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
oint
Expired
|
1.36 MB |
|
|
oint-deb
Expired
|
1.36 MB |
|