GUI acceptance tests using environment deployed from packages.

Build: #2211 failed

Job: Storage sync charts failed

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
2fd65918358f5f6055af9696e765eddae0bbdd9e
Total tests
1
Fixed in
#2212 (Changes by Bamboo Agent <bamboo@bamboo.onedata.org>)

Tests

  • 1 test in total
  • 1 test failed
  • 1 failure is new
  • 11 minutes taken in total.
New test failures 1
Status Test Duration
Collapse Failed test_storage_sync_charts test_user_configures_storage_sync_and_sees_storage_synchronization_statistics[1oz_1op_deployed]
11 mins
AssertionError: displayed 501 as number of deleted files on sync chart instead of expected 802
request = <FixtureRequest for <Function 'test_user_configures_storage_sync_and_sees_storage_synchronization_statistics[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: 
(34 more lines...)

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  4653  100  4653    0     0  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: b90817da3528: Container b90817da35283112295b3589ea821d565be982553611e82fe53e817a1e5ff5ba 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-CSSC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/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-CSSC/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-CSSC/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-CSSC/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
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
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
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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
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
W0708 09:23:14.103942     727 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  47479      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: 9434838f0a9e: Container 9434838f0a9e9e79083bdf4a5cf4813fe1f1d5cea427e4227a2c6189271775ac is not running
Error response from daemon: Cannot kill container: b7a15de78303: Container b7a15de78303c63d034f6849b69df95c7bf9256fdc27983a50f725794bbf0afd is not running
Error response from daemon: Cannot kill container: c217821ee87f: Container c217821ee87f8694673e022ceb7380e17817905964b522c779589817eed336d8 is not running
Error response from daemon: Cannot kill container: 5d34c10113fa: Container 5d34c10113fabb6cdfb60908750115b70c190980c7f480a2ebeaf33beffbdaa2 is not running
Error response from daemon: Cannot kill container: 60d69e3da087: Container 60d69e3da087d74ebf01eec6b98045b5d28ba440405c9b0a82d16e7174bafd56 is not running
Error response from daemon: Cannot kill container: 072391e1dee2: Container 072391e1dee2f91653b512195307af13617d2e16b240bfb9e06fbef779008703 is not running
Error response from daemon: Cannot kill container: 206e320327e3: Container 206e320327e3a94d9e9f55a36f37a8ac48d081615123cfee073b53efd198a46d is not running
Error response from daemon: Cannot kill container: 8353a9be1a54: Container 8353a9be1a54e246a3312405fd827b7ce677b7ac80f57bc9bfa5ba5d93dc8346 is not running
Error response from daemon: Cannot kill container: 221f42ad2668: Container 221f42ad2668de364b928a5cff678e6202bfc0e9de3e63bea7c52eabec7fc742 is not running
Error response from daemon: Cannot kill container: b42f9e3966e6: Container b42f9e3966e665afe19b02ee15e5b94b4a5f3758d513a9e8a34391fd3cf0030b is not running
Error response from daemon: Cannot kill container: 02c3aa2a53cf: Container 02c3aa2a53cf364683b622fd0a280054f405fb8ffc8aade1be0a2d3f5136d8ff is not running
Error response from daemon: Cannot kill container: 683cfec54a08: Container 683cfec54a08c71a82cfff445cd9a97858ffd449ceca8f7a5c28e4be2358aa4a is not running
Error response from daemon: Cannot kill container: 007c04fe974f: Container 007c04fe974fe6de5a47c52be32b3af79fa32aacbb325e1051199f1a50926b86 is not running
Error response from daemon: Cannot kill container: 92d3c0a07e84: Container 92d3c0a07e84abf66c139fa762b0070bb435e76932379dd9dc8f6478c0ab1c1a is not running
Error response from daemon: Cannot kill container: e0d142f6ed3b: Container e0d142f6ed3bb543fe133573cbac2a3a1527e20c37134dfa2d693ad5c629688e is not running
Error response from daemon: Cannot kill container: 6922788b4cde: Container 6922788b4cde616cdc5119e54d8364d9d40b1e0dc674c823a0e4924ca3fb08c5 is not running