Skip to content

Unskip tests related to files_primary_s3 ceph as the issue has been fixed #35601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DeepDiver1975 merged 1 commit into from
Jun 20, 2019
Merged

Unskip tests related to files_primary_s3 ceph as the issue has been fixed #35601

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions tests/acceptance/features/apiMain/checksums.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,6 @@ Feature: checksums
And user "user0" moves new chunk file with id "chunking-42" to "/myChunkedFile.txt" with checksum "SHA1:5d84d61b03fdacf813640f5242d309721e0629b1" using the WebDAV API
Then the HTTP status code should be "201"

@skipOnStorage:ceph @files_primary_s3-issue-128
Scenario: Upload new dav chunked file where checksum does not match
Given using new DAV path
When user "user0" creates a new chunking upload with id "chunking-42" using the WebDAV API
Expand All @@ -157,7 +156,6 @@ Feature: checksums
| fileId | /^[0-9a-z]{20,}$/ |
And the content of file "/myChunkedFile.txt" for user "user0" should be "BBBBBCCCCC"

@skipOnStorage:ceph @files_primary_s3-issue-128
Scenario: Upload new dav chunked file using async MOVE where checksum does not matches
Given using new DAV path
And the administrator has enabled async operations
Expand Down Expand Up @@ -191,7 +189,6 @@ Feature: checksums
| fileId | /^[0-9a-z]{20,}$/ |
And the content of file "/myChunkedFile.txt" for user "user0" should be "BBBBBCCCCC"

@skipOnStorage:ceph @files_primary_s3-issue-128
Scenario Outline: Upload a file where checksum does not match
Given using <dav_version> DAV path
And file "/chksumtst.txt" has been deleted for user "user0"
Expand Down Expand Up @@ -280,7 +277,6 @@ Feature: checksums
| old |
| new |

@skipOnStorage:ceph @files_primary_s3-issue-128
Scenario Outline: Uploading a file with invalid SHA1 checksum overwriting an existing file
Given using <dav_version> DAV path
When user "user0" uploads file "filesForUpload/textfile.txt" to "/textfile0.txt" with checksum "SHA1:f005ba11f005ba11f005ba11f005ba11f005ba11" using the WebDAV API
Expand All @@ -300,7 +296,6 @@ Feature: checksums
Then the HTTP status code should be "204"
And the content of file "/textfile0.txt" for user "user0" should be "BBBBBCCCCC"

@skipOnStorage:ceph @files_primary_s3-issue-128
Scenario: Upload overwriting a file with new chunking and invalid checksum
Given using new DAV path
When user "user0" creates a new chunking upload with id "chunking-42" using the WebDAV API
Expand Down