[
https://issues.apache.org/jira/browse/FLINK-34150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808183#comment-17808183
]
Matthias Pohl commented on FLINK-34150:
---------------------------------------
This issue is came up in FLINK-33923 because we noticed that the OpenSSL
dependency is installed for the e2e tests in the Azure Pipelines but we missed
it in the GitHub Actions migration. But that doesn't cause any issues because
the only OpenSSL-based e2e test is actually disabled. Merging FLINK-33914 would
have revealed the issue on {{master}} most likely after the corresponding S3
secrets are set.
> file sink e2e tests with local setup are not executed if s3 credentials are
> not provided
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-34150
> URL: https://issues.apache.org/jira/browse/FLINK-34150
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.17.2, 1.19.0, 1.18.1
> Reporter: Matthias Pohl
> Priority: Major
> Labels: test-stability
>
> While looking into test parity between Azure Pipelines and GitHub Actions, I
> noticed that the only OpenSSL-based test is
> {{flink-end-to-end-tests/test-scripts/test_file_sink.sh}} which comes with a
> local and a s3 setting.
> S3 requires S3 credential and the bucket information to be available through
> environment variables. That's handled in
> [flink-end-to-end-tests/test-scripts/common_s3.sh#L25|https://github.com/apache/flink/blob/8a9a08bf408aae8a33438a38614199efeb8f1c63/flink-end-to-end-tests/test-scripts/common_s3.sh#L25].
> The problem is that this shell script is also source'd when running the test
> with local setup (see
> [flink-end-to-end-tests/test-scripts/test_file_sink.sh#L27|https://github.com/apache/flink/blob/a6bea224ed012e5594ee755526f54ae7f3b0d22f/flink-end-to-end-tests/test-scripts/test_file_sink.sh#L27]).
> This means that also the local test is only running in the main repository
> which is not necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
