flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9564) Expose end-to-end module directory to test scripts
Date Tue, 12 Jun 2018 09:42:00 GMT

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

ASF GitHub Bot commented on FLINK-9564:
---------------------------------------

Github user zentol closed the pull request at:

    https://github.com/apache/flink/pull/6146


> Expose end-to-end module directory to test scripts
> --------------------------------------------------
>
>                 Key: FLINK-9564
>                 URL: https://issues.apache.org/jira/browse/FLINK-9564
>             Project: Flink
>          Issue Type: New Feature
>          Components: Tests
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>             Fix For: 1.6.0, 1.5.1
>
>
> Several end-to-end tests access jars from modules in {{flink-end-to-end-tests}}.
> To achieve this they use this hacky solutions like
> {{$TEST_DATA_DIR/../../<module>}} or {{$TEST_INFRA_DIR/../../<module>}}.
> This is brittle as hell can cause tests to fail by merely adding another directory layer.
> We should instead export the flink-end-to-end directory in the pre-commit/nightly scripts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message