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

[R] GitHub action fails on forks (R)

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • None
    • Developer Tools, R
    • None

    Description

      Starting on 2022-06-25, I began to receive daily emails from my GitHub fork of Arrow, alerting me to the following failing action:

      Upload R Nightly builds Upload R Nightly builds

      The action fails in Download Artifacts, with the following log content:

      Run if [ -z $PREFIX ]; then
      20nightly-packaging-2022-06-28-0
      21fatal: not a git repository (or any of the parent directories): .git
      22Downloading nightly-packaging-2022-06-28-0's artifacts.
      23Destination directory is /home/runner/work/arrow/arrow/binaries/nightly-packaging-2022-06-28-0
      2425[  state] Task / Branch                                               Artifacts
      26-------------------------------------------------------------------------------
      27[FAILURE] r-nightly-packages                                     uploaded 0 / 9
      28 └ https://github.com/ursacomputing/crossbow/runs/7091119162?check_suite_focus=true29 └ https://github.com/ursacomputing/crossbow/runs/7090086432?check_suite_focus=true30 └ https://github.com/ursacomputing/crossbow/runs/7090086299?check_suite_focus=true31 └ https://github.com/ursacomputing/crossbow/runs/7090086198?check_suite_focus=true32 └ https://github.com/ursacomputing/crossbow/runs/7090086062?check_suite_focus=true33 └ https://github.com/ursacomputing/crossbow/runs/7089567242?check_suite_focus=true34 └ https://github.com/ursacomputing/crossbow/runs/7088905795?check_suite_focus=true35 └ https://github.com/ursacomputing/crossbow/runs/7088905652?check_suite_focus=true36 └ https://github.com/ursacomputing/crossbow/runs/7088905551?check_suite_focus=true37 └ https://github.com/ursacomputing/crossbow/runs/7088905435?check_suite_focus=true38 └ https://github.com/ursacomputing/crossbow/runs/7088905110?check_suite_focus=true39 └ https://github.com/ursacomputing/crossbow/runs/7088895790?check_suite_focus=true40                   r-lib__libarrow__bin__windows__arrow-[0-9\.]+\.zip [MISSING]
      41                  r-lib__libarrow__bin__centos-7__arrow-[0-9\.]+\.zip [MISSING]
      42              r-lib__libarrow__bin__ubuntu-18.04__arrow-[0-9\.]+\.zip [MISSING]
      43              r-lib__libarrow__bin__ubuntu-22.04__arrow-[0-9\.]+\.zip [MISSING]
      44               r-pkg__bin__windows__contrib__4.1__arrow_[0-9\.]+\.zip [MISSING]
      45               r-pkg__bin__windows__contrib__4.2__arrow_[0-9\.]+\.zip [MISSING]
      46                r-pkg__bin__macosx__contrib__4.1__arrow_[0-9\.]+\.tgz [MISSING]
      47                r-pkg__bin__macosx__contrib__4.2__arrow_[0-9\.]+\.tgz [MISSING]
      48                         r-pkg__src__contrib__arrow_[0-9\.]+\.tar\.gz [MISSING]
      49ls: cannot access 'binaries/*/*/': No such file or directory
      50No files found. Stopping upload.
      51Error: Process completed with exit code 1. 

      In discussion with others, it appears to be impacting users who have forked Arrow. Note that I have not done any customization of GihHub actions, inheriting only what upstream provides. I also have not touched anything related to R.

      I have attempted to rebase on current tip of upstream and manually rerun the actions, but this produces the same result.

      Attachments

        Activity

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

          People

            Unassigned Unassigned Assign to me
            toddfarmer Todd Farmer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment