Acceptance tests using different clients concurrently. Environment deployed from packages.
Build: #653 failed Changes by Bartosz Walkowicz
Build result summary
Details
- Completed
- Queue duration
- 59 minutes
- Duration
- 35 minutes
- Labels
- None
- Revision
-
ff1fb21d4b702a6a181ec43747b4d1e8e64daba0
- Total tests
- 51
- Failing since
- #593 (Changes by Jakub Liput – )
- Fixed in
- #676 (Rebuilt by Bartosz Walkowicz)
Tests
- 0 New failures
- 2 Existing failures
- 0 Fixed
- 2 Quarantined / skipped
Responsible
This build has been failing since #593
No one has taken responsibility
Code commits
Configuration changes
Some of the jobs or stages referenced by this result no longer exist.
Tests
Status | Test | Failing since | View job | Duration | |
---|---|---|---|---|---|
test_onepanel_basic
test_revoke_space_support[1oz_1op_1oc-REST-web GUI-REST]
|
Failing since build #645 (Changes by Bamboo Agent <bamboo@cloud.plgrid.pl>) | Chrome onepanel tests | 37 secs | ||
TypeError: __init__() got an unexpected keyword argument 'mount_in_root' client1 = 'REST', client2 = 'web GUI', client3 = 'REST' request = <FixtureRequest for <Function 'test_revoke_space_support[1oz_1op_1oc-REST-web GUI-REST]'>> > ??? tests/mixed/scenarios/test_onepanel_basic.py:45: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ (46 more lines...) |
|||||
test_onepanel_basic
test_support_space[1oz_1op_1oc-REST-web GUI-REST]
|
Failing since build #645 (Changes by Bamboo Agent <bamboo@cloud.plgrid.pl>) | Chrome onepanel tests | 5 mins | ||
TypeError: __init__() got an unexpected keyword argument 'mount_in_root' client1 = 'REST', client2 = 'web GUI', client3 = 'REST' request = <FixtureRequest for <Function 'test_support_space[1oz_1op_1oc-REST-web GUI-REST]'>> from tests.gui.steps.oneprovider.file_browser import * > from tests.gui.steps.oneprovider.metadata import * tests/mixed/scenarios/test_onepanel_basic.py:41: (47 more lines...) |
Jira issues
Issue | Description | Status | |
---|---|---|---|
Unknown Issue Type | VFS-5956 | Could not obtain issue details from Jira |