GUI acceptance tests using environment deployed from packages.

Build: #1006 failed

Job: Storage sync failed

Job result summary

Completed
Duration
32 minutes
Revision
ee1179357e10b6b67904204643beb16e4b647dd8
Total tests
7
Failing since
#971 (Child of ODSRV-OZP-1376)
Fixed in
#1008 (Child of ODSRV-OZP-1389)

Tests

  • 7 tests in total
  • 3 tests failed
  • 1 failure is new
  • 2 tests were fixed
  • 26 minutes taken in total.
New test failures 1
Status Test Duration
Collapse Failed test_storage_sync test_user_does_not_see_files_and_directories_that_have_been_removed_in_storage_mount_point_when_delete_option_was_enabled[1oz_1op_deployed]
2 mins
AssertionError: no info notify with ".*[Ss]torage.*added.*" msg found
request = <FixtureRequest for <Function 'test_user_does_not_see_files_and_directories_that_have_been_removed_in_storage_mount_point_when_delete_option_was_enabled[1oz_1op_deployed]'>>

    @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: 
(56 more lines...)
Existing test failures 2
Status Test Failing since Duration
AssertionError: no info notify with ".*[Ss]torage.*added.*" msg found
request = <FixtureRequest for <Function 'test_user_sees_that_files_are_deleted_after_synchronization_when_delete_and_write_once_options_are_enabled[1oz_1op_deployed]'>>

    @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: 
(56 more lines...)
AssertionError: no info notify with ".*[Ss]torage.*added.*" msg found
request = <FixtureRequest for <Function 'test_user_sees_that_files_are_imported_to_depth_defined_by_update_configuration_if_it_is_larger_than_depth_of_import_configuration[1oz_1op_deployed]'>>

    @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: 
(56 more lines...)
Fixed tests 2
Status Test Failing since Duration
Successful test_storage_sync test_user_does_not_see_files_update_when_write_once_option_is_enabled[1oz_1op_deployed]
Failing since build #971 (Child of ODSRV-OZP-1376) 3 mins
Successful test_storage_sync test_user_sees_files_update_when_update_configuration_is_set[1oz_1op_deployed]
Failing since build #1005 (Changes by Bamboo Agent <bamboo@cloud.plgrid.pl>) 3 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
100  4419  100  4419    0     0  16040      0 --:--:-- --:--:-- --:--:-- 16069
Error response from daemon: Cannot kill container: 23d7a4d45ee1: Container 23d7a4d45ee10d8b89eafbfea6dd8d3e0f6156c30070a497f6337b3c13494f7e is not running
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
sh: 1: cannot create /var/lib/op_worker/gui_static/app-config.json: Directory nonexistent
sh: 1: cannot create /var/lib/oz_worker/gui_static/app-config.json: Directory nonexistent
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   4480      0 --:--:-- --:--:-- --:--:--  4477
Error from server (NotFound): pods "dev-elasticsearch-data-0" not found
Error from server (NotFound): pods "dev-elasticsearch-master-0" not found
Error response from daemon: Cannot kill container: ee15b4fc29a1: Container ee15b4fc29a137ecd53adaf07bfe6e6285fcf5d5a6a885ad0fbf160a024c8984 is not running
Error response from daemon: Cannot kill container: 8578800852f3: Container 8578800852f3f1f77c2233ef56f47ce4b7749e56d94df92b76abfc5cbe564784 is not running
Error response from daemon: Cannot kill container: baa29c4d70a1: Container baa29c4d70a1e7970a4da160b26f7babcba9726c6e4f7eb4c4fda0c447bf4b85 is not running
Error response from daemon: Cannot kill container: e3bdf8503083: Container e3bdf850308353a127a31634644cef323ee8c091d458a13354f668c9bfacaede is not running
Error response from daemon: Cannot kill container: c6cbc228bc9f: Container c6cbc228bc9f2abd8ab212835c43ce73ebfba5a5082105f62d2080ffe1198bac is not running
Error response from daemon: Cannot kill container: 1135820bb250: Container 1135820bb25022ecdfb1377d71762fb39252ddbb8d5b6c8420cad7cbdcccb2ec is not running
Error response from daemon: Cannot kill container: c7c63e53ae3c: Container c7c63e53ae3c36154fda4a75ed4ce400ab31ad70d8818c64a7679eb2c6e05b64 is not running
Error response from daemon: Cannot kill container: 35303683b6b5: Container 35303683b6b582d2129276f1f8a104696dc0486ef8756585a8f7c73878a51eb4 is not running
Error response from daemon: Cannot kill container: 32808690890f: Container 32808690890fca031352d2cad6bbc1b1c4ed0d71483411d681ab8ca084fc0902 is not running
Error response from daemon: Cannot kill container: e4f95b0856be: Container e4f95b0856beac71619b90c72d065a3a7b3ba1b8201a36e513a0b0d3007d5485 is not running
Error response from daemon: Cannot kill container: 0dd886673247: Container 0dd8866732479969b82ad2dc01bac47f9a51664759a2ed3a1cf03631fdea1f66 is not running
Error response from daemon: Cannot kill container: 6e86aff923f5: Container 6e86aff923f5cea95f5192348e78073a522523901ffcaf8aa343967f3f4d93cd is not running
Error response from daemon: Cannot kill container: 5ab394d81a5e: Container 5ab394d81a5e75f92b35f96a43c22f75d74aab0d427a2c718b7db0c8bfbe964e is not running
Error response from daemon: Cannot kill container: abc8a958b8e2: Container abc8a958b8e2aa698362a5e35dcd8f22855672716d83034f4aaae9e51a0b942e is not running
Error response from daemon: Cannot kill container: 164d23277b13: Container 164d23277b137c925f162ad37e46aeb2e3e961309a7428ed2898fe888c98eac6 is not running
Error response from daemon: Cannot kill container: 345d90451055: Container 345d90451055a5823a407f03b928a2e9d28f18f1fc689963fa75de7dc667c7b8 is not running
Error response from daemon: Cannot kill container: c25787b8d7b9: Container c25787b8d7b95bc1f7c785c75e2e0190fbdf7924b3c64c76a0d5d845778b19ce is not running
Error response from daemon: Cannot kill container: 93e9c2445404: Container 93e9c244540440b37ada6b690b9954f7372266c6fe2641eb39e6c997adcf07c6 is not running