GUI acceptance tests using environment deployed from packages.

Build: #15 failed

Job: Chrome onezone providers sync test failed

Job result summary

Completed
Duration
23 minutes
Revision
f95de5b0a2d5d8372d9c93421346e38993e49109
Total tests
4
Failing since
#4 (Child of ODSRV-OPRPM449-2)
Fixed in
#18 (Rebuilt by Natalia Organek)

Configuration changes

Job Chrome onezone providers sync test with key ODSRV-GAPT164-COPST no longer exists.

Tests

  • 4 tests in total
  • 2 tests failed
  • 1 test was fixed
  • 22 minutes taken in total.
Existing test failures 2
Status Test Failing since Duration
AssertionError: Synchronization is not done in given time
request = <FixtureRequest for <Function 'test_provider_with_stopped_workers_is_offline_and_resynchronises_with_others_after_restart[1oz_3op_providers_sync]'>>

    @pytest.mark.usefixtures(*function_args)
    def scenario_wrapper(request):
>       _execute_scenario(feature, scenario, request, encoding)

/usr/local/lib/python3.6/dist-packages/pytest_bdd/scenario.py:227: 
(28 more lines...)
AssertionError: Expected provider size: 5 GiB, actual: 5 GIB FREE OF 5 GIB
request = <FixtureRequest for <Function 'test_user_sees_right_capacity_sizes_for_each_provider_in_capacity_allocation_bar_in_space_providers_view[1oz_3op_providers_sync]'>>

    @pytest.mark.usefixtures(*function_args)
    def scenario_wrapper(request):
>       _execute_scenario(feature, scenario, request, encoding)

/usr/local/lib/python3.6/dist-packages/pytest_bdd/scenario.py:227: 
(26 more lines...)
Fixed tests 1
Status Test Failing since Duration
Successful test_onezone_providers_sync test_providers_synchronizes_after_supporting_space_with_yet_another_provider[1oz_3op_providers_sync]
Failing since build #14 (Child of ODSRV-OZP208-6) 4 mins

Error summary

The build generated some errors. See the full build log for more details.

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4419  100  4419    0     0  16661      0 --:--:-- --:--:-- --:--:-- 16612
Error response from daemon: Cannot kill container: 73c26f5c99c1: Container 73c26f5c99c10674e25006d3ee336f25e19333ff252857cf9d6e082e8fa6005c is not running
Error: No such container: 6c337a89a782
tput: unknown terminal "unknown"
Cloning into 'bamboos'...
Cloning into 'cdmi_swagger'...
Cloning into 'one_env'...
Cloning into 'onepanel_swagger'...
Cloning into 'bamboos'...
Cloning into 'oneprovider_swagger'...
Cloning into 'bamboos'...
Cloning into 'onezone_swagger'...
Cloning into 'bamboos'...
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4419  100  4419    0     0  16472      0 --:--:-- --:--:-- --:--:-- 16488
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 23d491556dea: Container 23d491556deacdf011cc19092806167fa4cb6b45b2145ce81a8fcb0af7babd34 is not running
Error response from daemon: Cannot kill container: 90a47a38feee: Container 90a47a38feee4bfee81997debf95fbc02bac5d15b9e86b876a066dba3fa9b2da is not running
Error response from daemon: Cannot kill container: 9ef9e1bea3a3: Container 9ef9e1bea3a3bddce82da6e1c1991ef32466a9b6bb35efb4fb8b7cb46393c2c5 is not running
Error response from daemon: Cannot kill container: ab943b065531: Container ab943b065531c00074e2ce1c10bef4b0ae0fcf4ed0dc3745670c90496a936b1b is not running
Error response from daemon: Cannot kill container: 93dff7a2fc49: Container 93dff7a2fc49c7f35dd9cdada9c89fc4409aa45752044f2d59f03bebe0c95d7c is not running
Error response from daemon: Cannot kill container: 265d4e80432f: Container 265d4e80432f36a194b6f0228aa1d808903ccc2039d19e1ac196d00f7cf5b499 is not running
Error response from daemon: Cannot kill container: b7eb95b7ff08: Container b7eb95b7ff08d7d420698da821cc056d49954f754b3c586cc0e97cdd0018dd0d is not running
Error response from daemon: Cannot kill container: c5c99639fa3e: Container c5c99639fa3e94cc205367711c2eeb77649cb4d949f099552ca329c63ab132d5 is not running
Error response from daemon: Cannot kill container: b4309a99b735: Container b4309a99b735de8b694524972fb8534a97368f5f1af118aa26b3739e6955699f is not running
Error response from daemon: Cannot kill container: e5fab83a066a: Container e5fab83a066a82c694ca69489bac09487e226485336e3d819fc0fbe9087cb606 is not running
Error response from daemon: Cannot kill container: 6f756be17932: Container 6f756be1793210d6500ad2dc1f001e6bd8c87e55aaf0cc42208b801e7ab1ea23 is not running
Error response from daemon: Cannot kill container: 9b8bbd0d189a: Container 9b8bbd0d189a7ad96b69e054a5b3e467716ba59edcf7cf276f006b38448cb16e is not running
Error response from daemon: Cannot kill container: 53f941699f22: Container 53f941699f22258eea1b70ae059848d8e04325e37c8756474700c45cf1437e68 is not running
Error response from daemon: Cannot kill container: 76fb0faf55c4: Container 76fb0faf55c4e81d823ab81949c865acffe7ff2e44d32112e8443fde2dde627b is not running
Error response from daemon: Cannot kill container: 14027ac4f00b: Container 14027ac4f00b0545a9c47682ef7c2fb7203a8882d21530611753c63fb407a0d6 is not running
Error response from daemon: Cannot kill container: 080d6f01d04b: Container 080d6f01d04b6d9dfd953f884984e91fa9310776c431b9d2d4276f1368e73f09 is not running
Error response from daemon: Cannot kill container: 0a9b1fe3a1e3: Container 0a9b1fe3a1e3dea2c438d29dadfa95ef6f92c29046a99d4a187d11a0214a4ce5 is not running
Error response from daemon: Cannot kill container: a43b5ff907af: Container a43b5ff907af8611f7c60e9eb84d46148b093c9f87f6a48df95ca14e53733bc7 is not running
Error response from daemon: Cannot kill container: 35c4b99d39e4: Container 35c4b99d39e4d3d4c11922467d0e5e11e7ec2c867faf324168e02664faa2445b is not running
Error response from daemon: Cannot kill container: 815c28e30f37: Container 815c28e30f3728d3c240e11a81dfc2adfb3fbf3ab82d66831a41f1ca2d0deae2 is not running
Error response from daemon: Cannot kill container: cca55b17b155: Container cca55b17b155e623057734ef4ad108af9576b3bce4d87cded0cb7f972a4da33a is not running
Error response from daemon: Cannot kill container: 6c101722593e: Container 6c101722593e904905ea6ca0aa9f15fee09e765aed0c33a5fb92cdce28a5aebd is not running
Error response from daemon: Cannot kill container: b218a3a4f05c: Container b218a3a4f05c99cf09af09b1ba97914083a2e084f470d0874f713072ce138b59 is not running
Error: No such container: c4aafec263b2