AssertionError: released size: 100 MiB  is not expected size: 20 B
request = <FixtureRequest for <Function 'test_user_uses_autocleaning_with_upper_size_limit_which_skips_too_big_files[1oz_2op_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: 
(36 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  38775      0 --:--:-- --:--:-- --:--:-- 38775
Error response from daemon: Cannot kill container: 2d9fbecb97f6: Container 2d9fbecb97f6f7b7fe599d9a9c06dbe91b589b5bf4e8881d720bfb554a037e39 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-CMMT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMMT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMMT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMMT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMMT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMMT/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-CMMT/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-CMMT/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-CMMT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
Error: could not find tiller
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)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
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)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
command terminated with exit code 126
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
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  16920      0 --:--:-- --:--:-- --:--:-- 16920
Error response from daemon: Cannot kill container: c67ad7128a59: Container c67ad7128a59132bbef0d7f2959fbcfdefa949e5d7994746ae9317896e9d0edb is not running
Error response from daemon: Cannot kill container: 4d585cbb4fc9: Container 4d585cbb4fc9e0f58edb3e5bcf201547a0ce7a3888c95121619838f9e7c5d2ff is not running
Error response from daemon: Cannot kill container: b990831a4b38: Container b990831a4b385a14c480e19f6251bfd236606fb559eab447630adacf7bbf91a9 is not running
Error response from daemon: Cannot kill container: 53bde0eaf776: Container 53bde0eaf776c44ac6fd40c348451e0d1cde4ee1c8320c2da5d4c3e8e4df5196 is not running
Error response from daemon: Cannot kill container: 848a8c06e895: Container 848a8c06e8957e080cc4175d0ccd775e56c2a6c1823da6aba275de60b56cdf79 is not running
Error response from daemon: Cannot kill container: 7086c32c00e8: Container 7086c32c00e85564f3e47592eb63b4feaf7f7327f3f3d3bdd82d9a6e2e6c4367 is not running
Error response from daemon: Cannot kill container: 6c088d83759f: Container 6c088d83759f013d77749a46120009c079430c3687be16788213a6442af26122 is not running
Error response from daemon: Cannot kill container: 27b99446d030: Container 27b99446d030b2108f398779a6a819356af49d3f156f40b0f5892f172deb0f4f is not running
Error response from daemon: Cannot kill container: 661a3ed612a2: Container 661a3ed612a250153f4fa5485b08e4cd68d29529e0121d88c9a54248edea04eb is not running
Error response from daemon: Cannot kill container: f8858e195f76: Container f8858e195f76ee49937c0c086a6b398719412d14b4fcda4e4f598802e54d1ac2 is not running
Error response from daemon: Cannot kill container: 1b2fa9b479fb: Container 1b2fa9b479fb20a278ab09490f0cc9f9fe4c4de736def21c10905f8a6ddec27e is not running
Error response from daemon: Cannot kill container: 3d5bf58d6e47: Container 3d5bf58d6e47d3e314b28e2739f1634c41e3f6851c68d54c805acfcfd39ffca3 is not running
Error response from daemon: Cannot kill container: f72b3652fdd4: Container f72b3652fdd4ea513301f1f6d8fb7be124a05fef15057053a0175e00414db295 is not running
Error response from daemon: Cannot kill container: 635100b90bc1: Container 635100b90bc18d8132350da686953af0991f14bbab6eb2aa40d60d1f98815f06 is not running
Error response from daemon: Cannot kill container: 5ba18b941c41: Container 5ba18b941c41e60d1db03e3eda89886112c927ca42eb739873810793525da6b1 is not running
Error response from daemon: Cannot kill container: e40821f841e0: Container e40821f841e03f1ca438bd166d17a5806c5ae3e19b779360dd1e8c1ec33924a1 is not running
Error response from daemon: Cannot kill container: 895a7280aebb: Container 895a7280aebbc3713ad6560044033f74313a3980f7302ce5b2267232f703da70 is not running
Error response from daemon: Cannot kill container: 6be34d33d05f: Container 6be34d33d05f5b1301009aa8b6799a154a5e4987b39db701f4e0e631d442daa5 is not running
Error response from daemon: Cannot kill container: ffade911a37b: Container ffade911a37b80ce9506be84165f322858c2f4c023d2fcdb63ebe0f9edc087f3 is not running