[
https://issues.apache.org/jira/browse/JCLOUDS-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365545#comment-16365545
]
Cservenak, Tamas commented on JCLOUDS-1380:
-------------------------------------------
[~gaul] Thanks for advice, am newbie with jclouds and Ceph in general.
Your comment made me run s3 api IT/Live tests too against our s3 api on 2.0.3
branch (992e60d82dc979c26a668079adda614e234434df):
{{Tests run: 144, Failures: 13, Errors: 0, Skipped: 10}}
Is better, so it really seems s3 is "better supported" than swift api (where
error rate I got was 1/4+ of all tests).
> Multiple IT/Live test failures with Openstack Swift
> ---------------------------------------------------
>
> Key: JCLOUDS-1380
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1380
> Project: jclouds
> Issue Type: Test
> Reporter: Cservenak, Tamas
> Priority: Major
> Attachments: openstack-swift-2.0.x.txt
>
>
> I have access to Openstack Swift instance and am planning to use JClouds to
> access it. Hence, just "for fun" I tried the IT/Live test suite against swift
> instance, and got several test failures.
> {{Tests run: 165, Failures: 36, Errors: 0, Skipped: 35}}
> Built the *master* branch of jclouds
> (88c84af8788116be2b1f492c3314e07b493dc6f2).
> How can I contribute to swift api improvements? Should I share the
> surefire-reports folder with failure details (is it enough? would it contain
> some sensitive data, ie. swift credentials/URLs I used?)
> Since am toying with 2.0.3 version, am planning to try the 2.0.x branch too.
> TIA
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
