You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2022/03/03 12:55:00 UTC
[jira] [Closed] (FLINK-26087) S3 filesystem tests could be enabled to run on PR AzureCI builds as well
[ https://issues.apache.org/jira/browse/FLINK-26087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Pohl closed FLINK-26087.
---------------------------------
Resolution: Duplicate
Closing this issue in favor of FLINK-12521
> S3 filesystem tests could be enabled to run on PR AzureCI builds as well
> ------------------------------------------------------------------------
>
> Key: FLINK-26087
> URL: https://issues.apache.org/jira/browse/FLINK-26087
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem
> Affects Versions: 1.15.0, 1.13.5, 1.14.3
> Reporter: Matthias Pohl
> Priority: Major
>
> When looking into FLINK-26015 I noticed that the {{FileSystemBehaviorTestSuite}} doesn't run because of missing S3 credentials. I checked it only for the {{HadoopS3FileSystemBehaviorITCase}} on {{master}} in [this build|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=31212&view=logs&j=d44f43ce-542c-597d-bf94-b0718c71e5e8&t=ed165f3f-d0f6-524b-5279-86f8ee7d0e2d], though:
> {code}
> 2022-02-11T07:35:43.3424031Z Feb 11 07:35:43 [INFO] Running org.apache.flink.fs.s3hadoop.HadoopS3RecoverableWriterExceptionITCase
> 2022-02-11T07:35:43.3574806Z Feb 11 07:35:43 [INFO] Running org.apache.flink.fs.s3hadoop.HadoopS3FileSystemBehaviorITCase
> 2022-02-11T07:35:43.9597611Z Feb 11 07:35:43 [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.604 s - in org.apache.flink.fs.s3hadoop.HadoopS3RecoverableWriterExceptionITCase
> 2022-02-11T07:35:43.9818566Z Feb 11 07:35:43 [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.612 s - in org.apache.flink.fs.s3hadoop.HadoopS3FileSystemBehaviorITCase
> 2022-02-11T07:35:44.6487150Z Feb 11 07:35:44 [ERROR] Picked up JAVA_TOOL_OPTIONS: -XX:+HeapDumpOnOutOfMemoryError
> 2022-02-11T07:35:44.6953455Z Feb 11 07:35:44 [ERROR] Picked up JAVA_TOOL_OPTIONS: -XX:+HeapDumpOnOutOfMemoryError
> 2022-02-11T07:35:45.0832407Z Feb 11 07:35:45 [INFO] Running org.apache.flink.fs.s3hadoop.HadoopS3FileSystemITCase
> 2022-02-11T07:35:45.1279447Z Feb 11 07:35:45 [INFO] Running org.apache.flink.fs.s3hadoop.HadoopS3RecoverableWriterITCase
> 2022-02-11T07:35:45.7356037Z Feb 11 07:35:45 [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.636 s - in org.apache.flink.fs.s3hadoop.HadoopS3FileSystemITCase
> 2022-02-11T07:35:45.8154233Z Feb 11 07:35:45 [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.677 s - in org.apache.flink.fs.s3hadoop.HadoopS3RecoverableWriterITCase
> 2022-02-11T07:35:46.1720757Z Feb 11 07:35:46 [INFO]
> 2022-02-11T07:35:46.1721277Z Feb 11 07:35:46 [INFO] Results:
> 2022-02-11T07:35:46.1721728Z Feb 11 07:35:46 [INFO]
> 2022-02-11T07:35:46.1722528Z Feb 11 07:35:46 [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> {code}
> I'd assume that this holds true for other test where {{S3TestCredentials.assumeCredentialsAvailable()}} is used. A {{MinioTestContainer}} was introduced as part of FLINK-26015 that could be utilized to work around this issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)