Matthias Pohl created FLINK-33468:
-
Summary: Run Kubernetes IT test fails due to wrong Maven version
Key: FLINK-33468
URL: https://issues.apache.org/jira/browse/FLINK-33468
Project: Flink
Makes sense. I will get in touch with the PMC once I raise the PR with the
tests.
Regards
Ram
On Wed, Dec 7, 2022 at 1:16 PM Matthias Pohl
wrote:
> You can implement the tests. Access to the underlying filesystem should be
> configurable through system properties (similar to what is done in
> A
You can implement the tests. Access to the underlying filesystem should be
configurable through system properties (similar to what is done in
AzureFileSystemBehaviorITCase). This enables contributors to run the tests
locally (if they set the corresponding resource up). You should reach out
to the F
Thank you for your email. So with this PR I should be adding ABFS related
config and secrets and also ensure that the existing WASB secrets are also
updated?
Regards
Ram
On Wed, Dec 7, 2022 at 1:51 AM Matthias Pohl
wrote:
> Hi Ramkrishna,
> There are Jira issues for the Azure e2e tests [1] and
Hi Ramkrishna,
There are Jira issues for the Azure e2e tests [1] and
AzureFileSystemBehaviorITCase [2]. Essentially, it comes down to setting
things up in Azure and working together with the PMC to add the secrets to
the Azure CI project.
The secrets are only set for CI on master and the release br
Hi devs,
I was trying to write test cases for the Streaming sink support for ABFS as
part of https://issues.apache.org/jira/browse/FLINK-30128.
I found that the AzureFileSystemBehaviorITCase was not running in the CI
build too. So if I want to add the Recoverable support for ABFS , is there
a way
jackylau created FLINK-18236:
Summary: flink elasticsearch IT test
ElasticsearchSinkTestBase.runElasticsearchSink* verify it not right
Key: FLINK-18236
URL: https://issues.apache.org/jira/browse/FLINK-18236
Zhenqiu Huang created FLINK-14982:
-
Summary: YARN IT Test Case log config is mistakenly disabled
Key: FLINK-14982
URL: https://issues.apache.org/jira/browse/FLINK-14982
Project: Flink
Issue
Andrey Zagrebin created FLINK-13169:
---
Summary: IT test for fine-grained recovery (task executor failures)
Key: FLINK-13169
URL: https://issues.apache.org/jira/browse/FLINK-13169
Project: Flink
Andrey Zagrebin created FLINK-13019:
---
Summary: IT test for fine-grained recovery
Key: FLINK-13019
URL: https://issues.apache.org/jira/browse/FLINK-13019
Project: Flink
Issue Type: Sub-task
vinoyang created FLINK-11277:
Summary: Queryable state IT test failed
Key: FLINK-11277
URL: https://issues.apache.org/jira/browse/FLINK-11277
Project: Flink
Issue Type: New Feature
Till Rohrmann created FLINK-10764:
-
Summary: Add S3 entropy injection end-to-end/IT test
Key: FLINK-10764
URL: https://issues.apache.org/jira/browse/FLINK-10764
Project: Flink
Issue Type
Tzu-Li (Gordon) Tai created FLINK-6867:
--
Summary: Elasticsearch 1.x IT test still instable due to embedded
node instability
Key: FLINK-6867
URL: https://issues.apache.org/jira/browse/FLINK-6867
Yes, I will take care of it as part other JIRA that I am working on.
RegardsVijay
On Wednesday, June 29, 2016 2:40 AM, Maximilian Michels
wrote:
Hi Vijay,
Glad we solved the problem.
Good catch with the FlinkYarnSessionCli. We should clean up the
properties file after running the Yarn
Hi Vijay,
Glad we solved the problem.
Good catch with the FlinkYarnSessionCli. We should clean up the
properties file after running the Yarn tests. If you want to fix that,
you could open a pull request.
Cheers,
Max
On Wed, Jun 29, 2016 at 1:34 AM, Vijay Srinivasaraghavan
wrote:
> Hi Max,
> Yo
Hi Max,
You are right. The uber jar is built in "intsall" or "package" stage and Yarn
test assumes the flink uber jar to pre-exist. We may have to document the steps
so that it will not be missed when someone else tries in the future.
I have also noticed errors with the "CliFrontendAddressConfigu
Hi Vijay,
Hasn't been failing for me whenever I pulled in the latest master.
Neither when I run "mvn clean verify" nor when I execute the test from
within IntelliJ. That said, there are some unstable tests that fail on
Travis.
>YARNSessionFIFOITCase.setup:71->YarnTestBase.startYARNWithConfig:343
I just pulled the latest code and ran below commands. Both of them failed and
it is consistent.
1) "mvn clean install"
Results :
Failed tests:
LocalFlinkMiniClusterITCase.testLocalFlinkMiniClusterWithMultipleTaskManagers:166
Thread Thread[initialSeedUniquifierGenerator,5,main] was started by
Hi,
the first command you mentioned doesn't work because the Yarn tests are not
executed in the traditional phases and therefore maven will complain. If
you do it like this it will work (I tried it):
mvn clean verify -pl flink-yarn-tests -Pinclude-yarn-tests
-Dtest=YARNSessionFIFOITCase#testJavaAP
I am on Ubuntu 16.x, Java OpenJDK 1.8.0_91.
Can you try below commands and see if its working with the latest trunk code.
mvn clean verify -pl flink-yarn-tests -Pinclude-yarn-tests
-Dtest=YARNSessionFIFOITCase#testJavaAPI
mvn clean install
RegardsVijay
On Monday, June 27, 2016 5:44 AM, Al
Hi,
I just ran a "mvn clean verify" and it passed on my machine (latest master,
OS X El Capitan, Java 1.8.0_40, Maven 3.3.9). What's your environment?
Cheers,
Aljoscha
On Fri, 24 Jun 2016 at 16:47 Vijay Srinivasaraghavan
wrote:
> I am seeing below failure consistently with the latest trunk code
I am seeing below failure consistently with the latest trunk code when I run
"mvn clean verify". Is anyone seeing similar error in your environment?
Failed tests:
LocalFlinkMiniClusterITCase.testLocalFlinkMiniClusterWithMultipleTaskManagers:166
Thread Thread[initialSeedUniquifierGenerator,5,ma
22 matches
Mail list logo
