You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2021/06/22 06:24:00 UTC
[jira] [Comment Edited] (FLINK-23078) Scheduler Benchmarks not
compiling
[ https://issues.apache.org/jira/browse/FLINK-23078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367034#comment-17367034 ]
Piotr Nowojski edited comment on FLINK-23078 at 6/22/21, 6:23 AM:
------------------------------------------------------------------
-I'm fixing the benchmark build-, but it looks like we are still referring in the flink-benchmarks repository to some internal flink classes. At the first glance it looks like this reference to {{TestingUtils}} could be removed, because each individual benchmark is defining it's own {{tearDown}} method that either already is doing, or could be doing the shutdown? [~Thesharing] [~chesnay] could you take a look at this?
was (Author: pnowojski):
I'm fixing the benchmark build, but it looks like we are still referring in the flink-benchmarks repository to some internal flink classes. At the first glance it looks like this reference to {{TestingUtils}} could be removed, because each individual benchmark is defining it's own {{tearDown}} method that either already is doing, or could be doing the shutdown? [~Thesharing] [~chesnay] could you take a look at this?
> Scheduler Benchmarks not compiling
> ----------------------------------
>
> Key: FLINK-23078
> URL: https://issues.apache.org/jira/browse/FLINK-23078
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks, Runtime / Coordination
> Affects Versions: 1.14.0
> Reporter: Piotr Nowojski
> Assignee: Chesnay Schepler
> Priority: Blocker
> Fix For: 1.14.0
>
>
> {code:java}
> 07:46:50 [ERROR] /home/jenkins/workspace/flink-master-benchmarks/flink-benchmarks/src/main/java/org/apache/flink/scheduler/benchmark/SchedulerBenchmarkBase.java:21:44: error: cannot find symbol
> {code}
> CC [~chesnay] [~Thesharing]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)