[
https://issues.apache.org/jira/browse/ARROW-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16400415#comment-16400415
]
ASF GitHub Bot commented on ARROW-2312:
---------------------------------------
TheNeuralBit commented on issue #1751: ARROW-2312: [JS] run test_js before
test_integration
URL: https://github.com/apache/arrow/pull/1751#issuecomment-373376135
@wesm I left a comment on the relevant JIRA:
https://issues.apache.org/jira/browse/ARROW-2266
We currently validate the arrow data with every JS target, and there's 9 or
10 of them. Maybe a solution could be to just pick one lowest common
denominator target for the CI tests, like es5-umd, then test every target as
part of the nightlies you've been discussing.
----------------------------------------------------------------
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:
[email protected]
> [JS] verify-release-candidate-sh must be updated to include JS in integration
> tests
> -----------------------------------------------------------------------------------
>
> Key: ARROW-2312
> URL: https://issues.apache.org/jira/browse/ARROW-2312
> Project: Apache Arrow
> Issue Type: Bug
> Components: JavaScript
> Reporter: Wes McKinney
> Assignee: Paul Taylor
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.9.0
>
>
> I was unable to run verify-release-candidate.sh when working on the first
> iteration of the 0.9.0 release.
> JavaScript was added to the integration tests, but the verification script
> has not been updated yet
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
