beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-5293) Unable to run IOIT on s3 filesystem
Date Mon, 03 Sep 2018 14:17:07 GMT


ASF GitHub Bot logged work on BEAM-5293:

                Author: ASF GitHub Bot
            Created on: 03/Sep/18 14:16
            Start Date: 03/Sep/18 14:16
    Worklog Time Spent: 10m 
      Work Description: iemejia commented on issue #6327: [BEAM-5293] Fix build break while
running IOIT on s3 filesystem
   @lgajowy I suppose there is nothing to validate that a branch not used by default is ok,
but I am far from a gradle wiz, @lukecwik you know if something can help to avoid this case?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 140575)
    Time Spent: 20m  (was: 10m)

> Unable to run IOIT on s3 filesystem
> -----------------------------------
>                 Key: BEAM-5293
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Lukasz Gajowy
>            Assignee: Lukasz Gajowy
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
> Due to change in gradle configuration (in BeamModulePlugin.groovy) it is now imposssible
to download dependencies necessary for s3 filesystem. Running results in a build error. 

This message was sent by Atlassian JIRA

View raw message