You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Micah Whitacre (JIRA)" <ji...@apache.org> on 2016/07/29 22:30:20 UTC

[jira] [Resolved] (CRUNCH-613) Fix FileTargetImplTest.testHandleOutputsMovesFilesToDestination instability

     [ https://issues.apache.org/jira/browse/CRUNCH-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Micah Whitacre resolved CRUNCH-613.
-----------------------------------
    Resolution: Fixed

Code has been pushed to master.

> Fix FileTargetImplTest.testHandleOutputsMovesFilesToDestination instability
> ---------------------------------------------------------------------------
>
>                 Key: CRUNCH-613
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-613
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>            Reporter: Clément MATHIEU
>            Assignee: Micah Whitacre
>             Fix For: 0.15.0
>
>         Attachments: CRUNCH-613.patch, CRUNCH-613b.patch
>
>
> {{FileTargetImplTest.testHandleOutputsMovesFilesToDestination}} consistently fails on my machine because it relies on the erroneous assumption that {{handleOutputs}} will preserve part indexes in file names.
> If you are lucky the {{part-m-00000}} file created by the MR job will be copied to the destination folder with the exact same name. However it just... luck. Final index only depends on  iterator order which can vary from machine to machine (OS, FS, JDK etc.)
> This test should be rewritten to not rely on a such erroneous assumption. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)