GUI acceptance tests using environment deployed from packages.

Build: #2075 was successful

Job: Transfers directories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
d5330e48531ab5bfbefefb1e446da4fe7cede649
Total tests
5
Successful since
#1990 ()

Tests

  • 5 tests in total
  • 12 minutes taken in total.

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  42300      0 --:--:-- --:--:-- --:--:-- 42300
Error response from daemon: Cannot kill container: 7dfbc5fdda58: Container 7dfbc5fdda5874a46b6831b6a6d1dcc5663a52fa685780650c30a16eecc22b72 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-CTD/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/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-CTD/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-CTD/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-CTD/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
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]
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  37224      0 --:--:-- --:--:-- --:--:-- 37224
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: c0d9e066e5d5: Container c0d9e066e5d5413c84845dc54399e501c68fc03a372354b5093bf226a055b950 is not running
Error response from daemon: Cannot kill container: 6ab00034e1f6: Container 6ab00034e1f685c8b082ff4e1217318a9c8fcbda3e1024b2475e8520f33c90bb is not running
Error response from daemon: Cannot kill container: 53709dba859a: Container 53709dba859a6c991023c1189ed30d734dff72b319c368b87dd7ea5b8084a80f is not running
Error response from daemon: Cannot kill container: d0c23021c0e0: Container d0c23021c0e02ad279c327eff8b2136ffae841917a20afc18edc51e2a915c86f is not running
Error response from daemon: Cannot kill container: acc3b8ebcf39: Container acc3b8ebcf39c23cf195dec019154b459aa5bd3e663090562a911a4b4853c769 is not running
Error response from daemon: Cannot kill container: 9f6b81c85c00: Container 9f6b81c85c00fae6562b4979d3fe27212e46b21d7ba1d9672638467fbc5666b5 is not running
Error response from daemon: Cannot kill container: 4907d3de12da: Container 4907d3de12da1cb5e15b0eeee5cf3f5d7aebf2b8fac91db219d3cdc5814229bd is not running
Error response from daemon: Cannot kill container: 361eb553ef72: Container 361eb553ef72141295b872d1455e7dfc84bf8ecc5f15df6ff1cf2011896839b9 is not running
Error response from daemon: Cannot kill container: 556b6f3a0fbe: Container 556b6f3a0fbebfb301dd41900123629e18c3b70c9325f3819fb8c5d23d9c46fc is not running
Error response from daemon: Cannot kill container: 77bcd854c9ac: Container 77bcd854c9acffa8aadb7cac2c4f816308705deee8f0cd890d0c97fac593b13e is not running
Error response from daemon: Cannot kill container: fe6774a7fd80: Container fe6774a7fd80c0c5f75082cbb33e3eece66b2f8f9dc586aad09c5e526548ca46 is not running
Error response from daemon: Cannot kill container: 0e278c5e4267: Container 0e278c5e426799130aca35f9355b42d5e5cc572090a8a74f0a5742fa748777b7 is not running
Error response from daemon: Cannot kill container: 25a43940939b: Container 25a43940939bab870330cdec2c3ef5957775f155912f780e05ad6438d593b53e is not running
Error response from daemon: Cannot kill container: ab165ac1471b: Container ab165ac1471b15320c34cc2471ca7b1b9319b330536bcf1053321114d7f7b8fb is not running
Error response from daemon: Cannot kill container: 5362e24913ca: Container 5362e24913caa9dd164e9c9d35878f77a9c96661ed3f76e6849d2b0c8ea5a042 is not running
Error response from daemon: Cannot kill container: d793e6069f56: Container d793e6069f565dd0d10421ed5e0a5eecbb1a87161f415bcc62a594150a8a5b5f is not running
Error response from daemon: Cannot kill container: b3833fab9649: Container b3833fab96495ddf5c3e83ba446c030ac146603f7c264b7990dd922eb0ad6803 is not running
Error response from daemon: Cannot kill container: 71693ec46448: Container 71693ec4644828c24d88b3cb6482e37aee55ae9ef6dbfc9526643bddc37f0e24 is not running
Error response from daemon: Cannot kill container: b85a71668586: Container b85a7166858604f73f5f876b405f4c147b1786a2eefb8c15305077dc026c708d is not running