2. TEST | Полное тестирование (RU) #49
Bayselonarrendoint_test_full_ru.yml
on: workflow_dispatch
Testing-Telegram
3m 25s
Testing-VK
3m 30s
Testing-Viber
2m 59s
Testing-Twitter
5m 26s
Testing-YandexDisk
6m 4s
Testing-Notion
3m 1s
Testing-Slack
3m 0s
Testing-Airtable
2m 58s
Testing-Dropbox
3m 9s
Testing-Bitrix24
3m 23s
Testing-VkTeams
3m 1s
Testing-Ozon
3m 1s
Testing-Neocities
3m 0s
Testing-CDEK
3m 3s
Testing-YandexMetrika
2m 58s
Testing-S3
3m 3s
Testing-TCP
3m 4s
Testing-GoogleCalendar
0s
Testing-GoogleDrive
0s
Testing-GoogleSheets
0s
Clear-Cache
2s
Annotations
111 errors and 23 warnings
|
Testing-Viber
Process completed with exit code 3.
|
|
Testing-Viber
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-GoogleWorkspace
Process completed with exit code 3.
|
|
Testing-YandexMetrika
Process completed with exit code 3.
|
|
Testing-YandexMetrika
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-Neocities
Process completed with exit code 3.
|
|
Testing-Neocities
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-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-Ozon
Process completed with exit code 3.
|
|
Testing-Ozon
Process completed with exit code 3.
|
|
Testing-Ozon
Process completed with exit code 3.
|
|
Testing-Ozon
Process completed with exit code 3.
|
|
Testing-Ozon
Process completed with exit code 3.
|
|
Testing-CDEK
Process completed with exit code 3.
|
|
Testing-CDEK
Process completed with exit code 3.
|
|
Testing-CDEK
Process completed with exit code 3.
|
|
Testing-S3
Process completed with exit code 3.
|
|
Testing-S3
Process completed with exit code 3.
|
|
Testing-S3
Process completed with exit code 3.
|
|
Testing-TCP
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-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-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-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-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.
|
|
Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Decode
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Viber
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Airtable
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-GoogleWorkspace
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-GoogleWorkspace
Cache save failed.
|
|
Testing-YandexMetrika
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Slack
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Neocities
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-VkTeams
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Notion
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Ozon
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-CDEK
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-S3
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-TCP
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Dropbox
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Telegram
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Bitrix24
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-VK
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-Twitter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Testing-YandexDisk
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Encode
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Clear-Cache
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|