You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2020/01/22 22:22:00 UTC

[jira] [Comment Edited] (BEAM-9172) Nexmark results for Flink are broken in our CI

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

Ismaël Mejía edited comment on BEAM-9172 at 1/22/20 10:21 PM:
--------------------------------------------------------------

After some more research It seems that by default the results are executed with Direct runner and the results are going to the TestFlinkRunner table, so no corrupted data, just invalid data in a wrong table.


was (Author: iemejia):
After some more research It seems that by default the results are executed with Direct runner and the results are going to the DirectRunner table, so no corrupted data, just twice the number of runs on direct runner during the last year :S

> Nexmark results for Flink are broken in our CI
> ----------------------------------------------
>
>                 Key: BEAM-9172
>                 URL: https://issues.apache.org/jira/browse/BEAM-9172
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Ismaël Mejía
>            Assignee: Ismaël Mejía
>            Priority: Minor
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> While reviewing the latest release I found that the Flink runner results in the [Nexmark dashboards|https://apache-beam-testing.appspot.com/explore?dashboard=5699257587728384] have not been updated since 2019/01 !!!
> This seems to be a problem with the way the PostCommit script resolves the id of the table from the given runner where it stores its data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)