selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: element is not attached to the page document   (Session info: chrome=78.0.3904.70)
request = <FixtureRequest for <Function 'test_user_sees_dataset_in_detached_tab_after_deleting_directory[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: 
(180 more lines...)

RuntimeError: waited too long
request = <FixtureRequest for <Function 'test_user_sees_directory_tree_in_dataset_browser_after_marking_directories_as_dataset[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: 
(44 more lines...)

selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: element is not attached to the page document   (Session info: chrome=78.0.3904.70)
request = <FixtureRequest for <Function 'test_user_fails_to_reattach_dataset_after_deleting_directory[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: 
(174 more lines...)

selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: element is not attached to the page document   (Session info: chrome=78.0.3904.70)
request = <FixtureRequest for <Function 'test_user_sees_dataset_in_attached_tab_after_reattaching_detached_dataset[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: 
(174 more lines...)

RuntimeError: waited too long
request = <FixtureRequest for <Function 'test_user_sees_directory_tree_in_detached_tab_after_detaching_directories[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: 
(38 more lines...)

  % 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  4653  100  4653    0     0  43485      0 --:--:-- --:--:-- --:--:-- 43485
Error response from daemon: Cannot kill container: 99ac5fb9ea15: Container 99ac5fb9ea152960fb39b89d85729ff60455f77152a983eae86207e0baf476c4 is not running
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'bamboos'
Submodule 'cdmi_swagger' (ssh://git@git.onedata.org:7999/vfs/cdmi-swagger.git) registered for path 'cdmi_swagger'
Submodule 'one_env' (ssh://git@git.onedata.org:7999/vfs/one-env.git) registered for path 'one_env'
Submodule 'onepanel_swagger' (ssh://git@git.onedata.org:7999/vfs/onepanel-swagger.git) registered for path 'onepanel_swagger'
Submodule 'oneprovider_swagger' (ssh://git@git.onedata.org:7999/vfs/oneprovider-swagger.git) registered for path 'oneprovider_swagger'
Submodule 'onezone_swagger' (ssh://git@git.onedata.org:7999/vfs/onezone-swagger.git) registered for path 'onezone_swagger'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onezone_swagger'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onepanel_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onepanel_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'oneprovider_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/oneprovider_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onezone_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
W1018 13:40:42.220753     395 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
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
100  4653  100  4653    0     0  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 41ad4d845411: Container 41ad4d845411e56f0bb820c243ac39073b897178a9f1bc3a63e2e959447e0b4a is not running
Error response from daemon: Cannot kill container: 7ac6f4f5cf96: Container 7ac6f4f5cf96ee49e4a69183d8d6e20415e6844a24971bb98be9fc86a84e8594 is not running
Error response from daemon: Cannot kill container: 302470a7dce5: Container 302470a7dce503ba3f6a67f11ddbc87143c756ae59f744306744f9babc6a85ff is not running
Error response from daemon: Cannot kill container: 3101932676fd: Container 3101932676fd2fe6b14a928fde4c429aec14970d208f635587911f533755687f is not running
Error response from daemon: Cannot kill container: e1b7a249ea0c: Container e1b7a249ea0ceeeb9b7a1d57c133ca301a5b56ff68f33e76401574fbb374fe94 is not running
Error response from daemon: Cannot kill container: 009e29d23305: Container 009e29d23305b253783bc2c67e6cd2bc8481491fb8b6915ec270cdcf93e03135 is not running
Error response from daemon: Cannot kill container: 58b061598165: Container 58b06159816596507094868addef00b7b0fd517a1f7a4769f3bf104654254b72 is not running
Error response from daemon: Cannot kill container: 7f035cea3f0e: Container 7f035cea3f0e1290126c4658d1c6113d1cc654bd8573036719122254e3e79507 is not running
Error response from daemon: Cannot kill container: 63f8d1e4536a: Container 63f8d1e4536ac6f5ea1ffa026728a45bb58f15cf5f4a10a7b82fcfc5835c1b52 is not running
Error response from daemon: Cannot kill container: 2226429fb2d8: Container 2226429fb2d868b359a06614f16aadf9b2ed9623e51d5f472342310c1179efbc is not running
Error response from daemon: Cannot kill container: 96757056784a: Container 96757056784a247ca21c0265c633479a9365ac7a4441a3affb72d5b673f83d75 is not running
Error response from daemon: Cannot kill container: b485cec2f915: Container b485cec2f9154cadf298032a46eb4bdcfa08cd4b0cefadcc5af2da6c3066e629 is not running
Error response from daemon: Cannot kill container: 17d6de3373a2: Container 17d6de3373a26c0625223ac91a2d30c77430711651d3cc6ea59934e41ca45f16 is not running
Error response from daemon: Cannot kill container: e73c40db0285: Container e73c40db02859e809c38fc360a329282abaf5edcd27693ea2336c717392ee01a is not running
Error response from daemon: Cannot kill container: 7979b0f8676b: Container 7979b0f8676b0820f6584a879e47607a1fffe054e56573fc1ff0b281a911748c is not running
Error response from daemon: Cannot kill container: 43d5fbb2b448: Container 43d5fbb2b44829f508a471a80f9d55683f5bba5959c11c5342a444109338bd0a is not running