2. TEST | Полное тестирование (EN) #103
oint_test_full_en.yml
on: workflow_dispatch
Testing-Telegram
3m 12s
Testing-VK
3m 17s
Testing-Viber
3m 4s
Testing-Twitter
5m 25s
Testing-YandexDisk
3m 0s
Testing-Notion
2m 56s
Testing-Slack
2m 59s
Testing-Airtable
3m 6s
Testing-Dropbox
3m 10s
Testing-Bitrix24
3m 9s
Testing-VkTeams
2m 57s
Testing-Ozon
3m 6s
Testing-GoogleCalendar
0s
Testing-GoogleDrive
0s
Testing-GoogleSheets
0s
Clear-Cache
3s
Annotations
124 errors and 31 warnings
Testing-GoogleWorkspace
Process completed with exit code 3.
|
Testing-GoogleWorkspace
Process completed with exit code 3.
|
Testing-GoogleWorkspace
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-Notion
Process completed with exit code 3.
|
Testing-VkTeams
Process completed with exit code 3.
|
Testing-VkTeams
Process completed with exit code 3.
|
Testing-VkTeams
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-Slack
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-YandexDisk
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Viber
Process completed with exit code 3.
|
Testing-Ozon
Process completed with exit code 3.
|
Testing-Ozon
Process completed with exit code 3.
|
Testing-Airtable
Process completed with exit code 3.
|
Testing-Airtable
Process completed with exit code 3.
|
Testing-Airtable
Process completed with exit code 3.
|
Testing-Airtable
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Dropbox
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Bitrix24
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-Telegram
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-VK
Process completed with exit code 3.
|
Testing-Twitter
Process completed with exit code 3.
|
Testing-Twitter
Process completed with exit code 3.
|
Testing-Twitter
Process completed with exit code 3.
|
Testing-Twitter
Process completed with exit code 3.
|
Testing-Twitter
Process completed with exit code 3.
|
Testing-Twitter
Process completed with exit code 3.
|
Testing-Twitter
Process completed with exit code 3.
|
Build
The following actions use a deprecated Node.js version and will be forced to run on node20: otymko/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Decode
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-GoogleWorkspace
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-GoogleWorkspace
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-GoogleWorkspace
Cache save failed.
|
Testing-Notion
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. 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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-VkTeams
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-VkTeams
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Slack
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-Slack
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-YandexDisk
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-YandexDisk
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Viber
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. 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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Ozon
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-Ozon
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Airtable
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-Airtable
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Dropbox
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-Dropbox
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Bitrix24
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Testing-Bitrix24
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Telegram
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. 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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-VK
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. 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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Testing-Twitter
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. 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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, otymko/[email protected], actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Encode
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Encode
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
oint
Expired
|
142 KB |
|