[ 
https://issues.apache.org/jira/browse/FLINK-30426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647975#comment-17647975
 ] 

Martijn Visser commented on FLINK-30426:
----------------------------------------

[~Sergey Nuyanzin] Would be great. See 
https://github.com/apache/flink-connector-pulsar for the repo

You can find a failed run in 
https://github.com/apache/flink-connector-pulsar/actions/runs/3695837014/jobs/6258724442
 which I can reproduce locally by running the same Maven command as the CI does:

mvn clean deploy -Dscala-2.12 -Prun-end-to-end-tests 
-DdistDir=/path-to-flink-dist/flink-1.17-SNAPSHOT 
-Dflink.convergence.phase=install -Pcheck-convergence 
-Darchunit.freeze.store.default.allowStoreUpdate=false 
-Dlog4j.configurationFile=file:///path-to/flink-connector-pulsar/tools/ci/log4j.properties

For the {{v3.0}} branch it does pass. Command is the same, expect the 
distribution dir value of course. 



> Archunit can't find any tests in Pulsar repository
> --------------------------------------------------
>
>                 Key: FLINK-30426
>                 URL: https://issues.apache.org/jira/browse/FLINK-30426
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Pulsar
>    Affects Versions: pulsar-4.0.0
>            Reporter: Martijn Visser
>            Priority: Blocker
>
> CI is failing on {{main}} with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project flink-connector-pulsar: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test failed: 
> org.junit.platform.commons.JUnitException: TestEngine with ID 'archunit' 
> failed to discover tests: 'java.lang.Object 
> com.tngtech.archunit.lang.syntax.elements.MethodsThat.areAnnotatedWith(java.lang.Class)'
>  -> [Help 1]
> {code}
> It does work for {{v3.0}} but there's no obvious difference between the two 
> branches that might explain this issue. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to