Uploaded image for project: 'Apache Arrow'
  1. Apache Arrow
  2. ARROW-7255

[CI] Run source release test on pull request

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            kou Kouhei Sutou Assign to me
            kou Kouhei Sutou
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 40m
              40m

              Slack

                Issue deployment