You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Kouhei Sutou (Jira)" <ji...@apache.org> on 2019/11/25 20:57:00 UTC
[jira] [Updated] (ARROW-7255) [CI] Run source release test on pull
request
[ https://issues.apache.org/jira/browse/ARROW-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kouhei Sutou updated ARROW-7255:
--------------------------------
Description:
If we don't run source release test on pull request, it's difficult that we detect source release test failure on pull request.
For example,
https://github.com/apache/arrow/pull/5852 introduced source release test failure but we can't detect it on pull request.
Then
https://github.com/apache/arrow/pull/5889 tried to fix the source release test failure and merged but it didn't fix the failure. We couldn't detect it because we didn't run source release test on pull request.
Then
https://github.com/apache/arrow/pull/5893 will really fix the source release test failure.
Why did we not run source release test?
https://github.com/apache/arrow/pull/5889#issuecomment-558096239
> The reason why I've removed them from running on each PR to reduce the number of the triggered builds. See the mailing list thread about the queueing concerns. The docs build takes fairly long time, in contrary of the source release test.
The mailing list discussion:
[CI] Docker-compose refactor and GitHub Actions
https://lists.apache.org/thread.html/8fefdebd76742fe4ffb2ee7d0fa88ddf2b3229c55935c146b0d97e52@%3Cdev.arrow.apache.org%3E
was:
If we don't run source release test on pull request, it's difficult that we detect source release test failure on pull request.
For example,
https://github.com/apache/arrow/pull/5852 introduced source release test failure but we can't detect it on pull request.
Then
https://github.com/apache/arrow/pull/5889 tried to fix the source release test failure and merged but it didn't fix the failure. We couldn't detect it because we didn't run source release test on pull request.
Then
https://github.com/apache/arrow/pull/5893 will really fix the source release test failure.
> [CI] Run source release test on pull request
> --------------------------------------------
>
> Key: ARROW-7255
> URL: https://issues.apache.org/jira/browse/ARROW-7255
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Continuous Integration
> Reporter: Kouhei Sutou
> Assignee: Kouhei Sutou
> Priority: Major
>
> If we don't run source release test on pull request, it's difficult that we detect source release test failure on pull request.
> For example,
> https://github.com/apache/arrow/pull/5852 introduced source release test failure but we can't detect it on pull request.
> Then
> https://github.com/apache/arrow/pull/5889 tried to fix the source release test failure and merged but it didn't fix the failure. We couldn't detect it because we didn't run source release test on pull request.
> Then
> https://github.com/apache/arrow/pull/5893 will really fix the source release test failure.
> Why did we not run source release test?
> https://github.com/apache/arrow/pull/5889#issuecomment-558096239
> > The reason why I've removed them from running on each PR to reduce the number of the triggered builds. See the mailing list thread about the queueing concerns. The docs build takes fairly long time, in contrary of the source release test.
> The mailing list discussion:
> [CI] Docker-compose refactor and GitHub Actions
> https://lists.apache.org/thread.html/8fefdebd76742fe4ffb2ee7d0fa88ddf2b3229c55935c146b0d97e52@%3Cdev.arrow.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)