Build: #5 failed Changes by plgcwiertni <cwiertnia.michal@gmail.com>
Build result summary
Details
- Completed
- Queue duration
- 1 second
- Duration
- 67 minutes
- Labels
- None
- Revision
-
b70bdce635099aab50c27539cc19bb8cc1ddd83c
- Total tests
- 59
- Failing since
- #2 (Manual run by Michał Ćwiertnia – )
Tests
- 0 New failures
- 2 Existing failures
- 0 Fixed
Responsible
This build has been failing since #2
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_oneprovider_acl_dir_multi
test_read_directory_metadata[group-group1-fails-all except [read metadata]]
|
Failing since build #4 (Changes by plgcwiertni <cwiertnia.michal@gmail.com>) | Chrome oneprovider ACL directories multi | 1 min | ||
RuntimeError: no BASIC item found in MetadataRow in file browser in DataTab in Oneprovider page privileges = 'all except [read metadata]', subject_type = 'group' result = 'fails', subject_name = 'group1' request = <FixtureRequest for <Function 'test_read_directory_metadata[group-group1-fails-all except [read metadata]]'>> > ??? tests/gui/scenarios/test_oneprovider_acl_dir_multi.py:69: (33 more lines...) |
|||||
test_oneprovider_acl_dir_multi
test_read_directory_metadata[user-user2-fails-all except [read metadata]]
|
Failing since build #4 (Changes by plgcwiertni <cwiertnia.michal@gmail.com>) | Chrome oneprovider ACL directories multi | 1 min | ||
RuntimeError: no BASIC item found in MetadataRow in file browser in DataTab in Oneprovider page privileges = 'all except [read metadata]', subject_type = 'user' result = 'fails', subject_name = 'user2' request = <FixtureRequest for <Function 'test_read_directory_metadata[user-user2-fails-all except [read metadata]]'>> > ??? tests/gui/scenarios/test_oneprovider_acl_dir_multi.py:69: (33 more lines...) |
Jira issues
Issue | Description | Status | |
---|---|---|---|
Unknown Issue Type | VFS-4307 | Could not obtain issue details from Jira |