ningyougang opened a new issue #4587: S3AttachmentStoreMinioTests test cases run failed URL: https://github.com/apache/openwhisk/issues/4587 ### Problems When run ` ./gradlew :tests:test --tests="org.apache.openwhisk.core.database.s3.S3AttachmentStoreMinioTests" `, it is failed, e.g. ``` org.apache.openwhisk.core.database.s3.S3AttachmentStoreMinioTests STANDARD_OUT test router? false Started minio on 33657 Created bucket test-ow-travis org.apache.openwhisk.core.database.s3.S3AttachmentStoreMinioTests > S3MinioArtifactStore attachments should generate different attachment name on update STANDARD_OUT [2019-08-20T09:44:49.513Z] [WARN] Detected possible incompatible versions on the classpath. Please note that a given Akka HTTP version MUST be the same across all modules of Akka HTTP that you are using, e.g. if you use [10.1.8] all other modules that are released together MUST be of the same version. Make sure you're using a compatible set of libraries. Possibly conflicting versions [10.1.8, 10.1.5] in libraries [akka-http-spray-json:10.1.8, akka-parsing:10.1.8, akka-http2-support:10.1.5, akka-http-testkit:10.1.8, akka-http-xml:10.1.8, akka-http:10.1.8, akka-http-core:10.1.8] [2019-08-20T00:44:45.946Z] [INFO] [#tid_sid_unknown] [WhiskConfig] reading properties from file /home1/irteamsu/.jenkins/workspace/lambda-pr-build/whisk.properties [2019-08-20T00:44:45.959Z] [DEBUG] [#tid_sid_unknown] [WhiskConfig] properties file set value for runtimes.manifest [2019-08-20T00:44:46.489Z] [INFO] [#tid_sid_testing] [SimpleExec] Running command: /usr/bin/docker run -d -e MINIO_ACCESS_KEY=TESTKEY -e MINIO_SECRET_KEY=TESTSECRET -p 33657:9000 minio/minio server /data [2019-08-20T00:44:47.700Z] [DEBUG] [#tid_sid_testing] [SimpleExec] Done running command: /usr/bin/docker run -d -e MINIO_ACCESS_KEY=TESTKEY -e MINIO_SECRET_KEY=TESTSECRET -p 33657:9000 minio/minio server /data [2019-08-20T00:44:48.702Z] [INFO] [#tid_sid_unknown] [S3AttachmentStore] Initializing S3AttachmentStore with bucket=[test-ow-travis], prefix=[whiskentity], signer=[None] [2019-08-20T00:44:48.805Z] [INFO] [#tid_sid_unknown] [MemoryArtifactStore] Created MemoryStore for [whisks] [2019-08-20T00:44:49.139Z] [INFO] [#tid_1] [WhiskAction] write initiated on new cache entry [2019-08-20T00:44:49.258Z] [INFO] [#tid_1] [S3AttachmentStore] [ATT_PUT] uploading attachment '11a46f13-8c96-44f0-a46f-138c9624f0a6' of document 'id: null_ns_IGPeg/attachment_unique' [marker:database_saveDocumentAttachment_start:583] [2019-08-20T00:44:50.136Z] [ERROR] [#tid_1] [StoreUtils] [ATT_PUT] 'whiskentity' internal error, name: '11a46f13-8c96-44f0-a46f-138c9624f0a6', doc: 'null_ns_IGPeg/attachment_unique', failure: 'One or more of the specified parts could not be found. The part may not have been uploaded, or the specified entity tag may not match the part's entity tag.' [S3Exception] [marker:database_saveDocumentAttachment_error:1462:828] [2019-08-20T00:44:50.138Z] [INFO] [#tid_1] [WhiskAction] invalidating CacheKey(null_ns_IGPeg/attachment_unique) org.apache.openwhisk.core.database.s3.S3AttachmentStoreMinioTests > S3MinioArtifactStore attachments should generate different attachment name on update FAILED org.scalatest.exceptions.TestFailedException: The future returned an exception of type: akka.stream.alpakka.s3.S3Exception, with message: One or more of the specified parts could not be found. The part may not have been uploaded, or the specified entity tag may not match the part's entity tag.. at org.scalatest.concurrent.Futures$FutureConcept.tryTryAgain$1(Futures.scala:531) ... Caused by: akka.stream.alpakka.s3.S3Exception: One or more of the specified parts could not be found. The part may not have been uploaded, or the specified entity tag may not match the part's entity tag. (Code: InvalidPart, RequestID: , HostID: ) ``` It is strang that last week, i ran the test cases, it is successful, and i didn't change anything for the build machine and the codes. I run it on the other machines, it is successful, it seems it happened on the build machine. Regarding the build machine, when i am trying to find the reason, i did below things on the build machine, * reboot the machine, ran test again, tests showed same errors * reinstall docker, ran test again, tests showed same errors * ran minio locally(without docker), tests showed same errors * ran minio on an another host(using docker), all tests were passed Does someone meet the strange problem? or any idea for this?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
