Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15697
For the specific failure here, it was due to not syncing the latest version
between the releases for Winodws and the others (when R 3.3.2 was released). As
we use a fixed version, R 3.3.1 now (not the latest but old one), we wouldn't
meet the same case for the same reason in the future (I described this problem
in more details in https://github.com/apache/spark/pull/15709).
However, I guess you meant the concern of re-triggering the spurious
failures in general. For re-triggering tests, I am still looking into this
deeper. Will make a INFRA JIRA as soon as I figure out the way committers can
re-trigger. Current ways I have figured out so far as a (ugly) workaround are,
- Use another AppVeyor account
- Closing and then re-opening to launch another build.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
