Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/22098
>
> Ah, @shaneknapp <https://github.com/shaneknapp>, probably one possibility
> about the motivation is that we don't touch build configuration often and
> control the build time within the codebase so that committers don't have
to
> bother you every time it needs. For instance, although I know how to
> control the build time too, I don't touch them.
>
> that makes sense, but at the same time, it does require coordination to
happen between the timeout in the test framework and setting the jenkins
(absolute timeout)... which literally is just adding another step to the
process.
> Shall we just keep the current way and discuss if we happen to increase it
> again? I think 400m looks very enough as a limit, and we will put some
> efforts to reduce or keep the current limit I believe.
>
> sure, this works for me. and seeing that our builds are now taking
upwards of ***6*** hours, i'd rather have a conversation about build
strategy before revisiting this. :)
>
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
