According to my observations, many failures are caused by SocketTimeOut
exceptions.
So maybe we need to add timeout & retry logic for such test cases.

Best,
Liya Fan

On Mon, Apr 20, 2020 at 11:13 AM Francis Chuang <[email protected]>
wrote:

> Does the Github Actions tests always pass when this happens?
>
> I wonder if this is due to a network issue or a corrupt gradle cache on
> the travis nodes.
>
> See: https://github.com/facebook/react-native/issues/21130
>
> On 20/04/2020 12:58 pm, XING JIN wrote:
> > I have force pushed several times, but it keeps failing.
> >
> > Chunwei Lei <[email protected]> 于2020年4月20日周一 上午10:49写道:
> >
> >> I am a little confused too. Sometimes the traivs ci build of master
> fails
> >> when I merge
> >> the pr which passes all tests.
> >>
> >>
> >>
> >> Best,
> >> Chunwei
> >>
> >>
> >> On Mon, Apr 20, 2020 at 10:33 AM XING JIN <[email protected]>
> wrote:
> >>
> >>> In PR https://github.com/apache/calcite/pull/1926 and
> >>> https://github.com/apache/calcite/pull/1925, The Travis CI build keeps
> >>> failing with below messages. The exception has nothing to do with the
> >>> change in PR. There seems to be something wrong with the building
> >>> environment.
> >>>
> >>> ...
> >>>
> >>>
> >>
> /home/travis/build/apache/calcite/spark/src/main/java/org/apache/calcite/adapter/spark/HttpServer.java:42:
> >>> error: cannot access java.lang
> >>> class HttpServer {
> >>> ^
> >>>    zip END header not found
> >>>
> >>>
> >>
> /home/travis/build/apache/calcite/spark/src/main/java/org/apache/calcite/adapter/spark/HttpServer.java:43:
> >>> error: cannot find symbol
> >>>    private static String localIpAddress;
> >>>                   ^
> >>>    symbol:   class String
> >>>    location: class HttpServer
> >>>
> >>>
> >>
> /home/travis/build/apache/calcite/spark/src/main/java/org/apache/calcite/adapter/spark/HttpServer.java:45:
> >>> error: cannot find symbol
> >>>    private final File resourceBase;
> >>>                  ^
> >>>    symbol:   class File
> >>>    location: class HttpServer
> >>> ...
> >>>
> >>> Jin
> >>>
> >>
> >
>

Reply via email to