I have just reported this issue at the TravisCI forum.
https://travis-ci.community/t/s390x-jobs-have-not-been-almost-executed/10581
Regards,
Kazuaki Ishizaki,
Sutou Kouhei wrote on 2020/11/16 10:02:18:
> From: Sutou Kouhei
> To: dev@arrow.apache.org
> Date: 2020/11/16 10:02
> Subject:
Hi,
> 1. Is anyone else knows about these failures?
"these failures" means that the Travis CI jobs aren't ran,
right? (It doesn't mean that the Travis CI jobs reports
"failure".)
This may be a Travis CI bug.
> 2. Should we look into disabling these checks for PRs that only touch rust
> code? I
@Gidon
Copied the gist to a google doc for commenting:
https://docs.google.com/document/d/11qz84ajysvVo5ZAV9mXKOeh6ay4-xgkBrubggCP5220/edit#
@Micah
> it would be preferable to put them in an internal namespace to ensure
adequate unit testing is in place.
Agreed; my intent was only to indicate
Sorry if this has already been discussed.
There seems to be something wrong with the Travis CI jobs on some Arrow PRs
-- for example,
https://github.com/apache/arrow/pull/8662/checks?check_run_id=1400052607.
They go into the "pending" state and never seem to actually run.
Since these appear to
Arrow Build Report for Job nightly-2020-11-15-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-11-15-0
Failed Tasks:
- conda-win-vs2017-py36:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-11-15-0-azure-conda-win-vs2017-py36
-
