"File exists @ dir_s_mkdir " ruby exception when the deploy branch doesn't exist

joshuaavalon · November 30, 2018, 10:06am

It seems like there are some wrong with dpl-pages instead of my config.

Job: https://travis-ci.org/joshuaavalon/cloudflare-ddns/jobs/461701889
Log:

/home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.6/lib/dpl/provider/pages.rb:141:in `mkdir': File exists @ dir_s_mkdir - /tmp/d20181130-3845-gyh65z/work (Errno::EEXIST)
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.6/lib/dpl/provider/pages.rb:141:in `github_pull_or_init'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.6/lib/dpl/provider/pages.rb:195:in `block in push_app'
	from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/tmpdir.rb:89:in `mktmpdir'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.6/lib/dpl/provider/pages.rb:190:in `push_app'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.6/lib/dpl/provider.rb:199:in `block in deploy'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.6/lib/dpl/cli.rb:41:in `fold'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.6/lib/dpl/provider.rb:199:in `deploy'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.6/lib/dpl/cli.rb:32:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.6/lib/dpl/cli.rb:7:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.6/bin/dpl:5:in `<top (required)>'
	from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `load'
	from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `<main>'

config

dist: xenial
language: python
python: 3.7
stages:
  - test
  - build
jobs:
  include:
    - stage: test
      name: flake8
      install:
        - travis_retry pip install -r requirements.txt
        - travis_retry pip install -U flake8
      script:
        - flake8 --version
        - flake8 cloudflare_ddns
        - flake8 run.py
    - stage: test
      name: pylint
      before_install:
        - deactivate
        - /opt/python/3.7.1/bin/python -m venv ~/venv
        - source ~/venv/bin/activate
      install:
        - travis_retry pip install -r requirements.txt
        - travis_retry pip install -U pylint
      script:
        - pylint --version
        - pylint cloudflare_ddns
        - pylint run.py
    - stage: build
      name: mkdocs
      if: branch = master
      install:
        - travis_retry pip install -U mkdocs mkdocs-material
      script:
        - mkdocs build
      deploy:
        provider: pages
        skip-cleanup: true
        github-token: $GITHUB_TOKEN
        keep-history: true
        local-dir: site
        on:
          branch: master

joshuaavalon · December 3, 2018, 6:48am

Apparently, it only fail in Xenial. Switch to Trusty on deploy fixes the issue.

biodranik · March 11, 2019, 6:11am

I have exactly the same error with gh-pages deployment after switching from Trusty to Xenial.
The issue arises when github repo does not yet have a target branch (e.g. gh-pages).

Sam-Martin · May 18, 2019, 10:40am

So is there a better fix than switching back to Trusty?

BanzaiMan · May 29, 2019, 6:42pm

Hello, there. Does it still happen with dpl 1.10.10? If so, please provide a relevant URL. Thanks.

azubieta · June 4, 2019, 10:49pm

Not sure of which version of dpl is being used but here is the logs links:
https://travis-ci.org/AppImage/libappimage/jobs/541477197#L890

Please let me know if you need something else.

BanzaiMan · June 5, 2019, 7:16pm

The error is here

github.com

travis-ci/dpl/blob/v1.10.11/lib/dpl/provider/pages.rb#L141


def github_pull_or_init(target_dir)
  unless @keep_history
    github_init(target_dir)
    return
  end


  print_step "Trying to clone a single branch #{@target_branch} from existing repo..."
  unless context.shell "git clone --quiet --branch='#{@target_branch}' --depth=1 '#{gh_remote_url}' '#{target_dir}' > /dev/null 2>&1"
    # if such branch doesn't exist at remote, init it from scratch
    print_step "Cloning #{@target_branch} branch failed"
    Dir.mkdir(target_dir)  # Restore dir destroyed by failed `git clone`
    github_init(target_dir)
  end
end


def github_init(target_dir)
  FileUtils.cd(target_dir, :verbose => true) do
    print_step "Creating a brand new local repo from scratch in dir #{Dir.pwd}..."
    context.shell "git init" or raise 'Could not create new git repo'
    print_step 'Repo created successfully'
    context.shell "git checkout --orphan '#{@target_branch}'" or raise 'Could not create an orphan git branch'

I think there is a logical failure; when git clone fails, it usually fails with the destination directory created and half populated. This results in the exception.

daggerok · June 16, 2019, 3:24pm

hey!

so what with that issue? can we fix it on dist: xenial?

Installing deploy dependencies
Successfully installed multipart-post-2.1.1
Successfully installed faraday-0.15.4
Successfully installed public_suffix-3.0.3
Successfully installed addressable-2.6.0
Successfully installed sawyer-0.8.2
Successfully installed octokit-4.6.2
Successfully installed dpl-pages-1.10.11
7 gems installed
Logged in as @daggerok (Maksim Kostromin)

Preparing deploy

Deploying application
/home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.11/lib/dpl/provider/pages.rb:141:in `mkdir': File exists @ dir_s_mkdir - /tmp/d20190616-8171-g9thkk/work (Errno::EEXIST)
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.11/lib/dpl/provider/pages.rb:141:in `github_pull_or_init'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.11/lib/dpl/provider/pages.rb:195:in `block in push_app'
	from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/tmpdir.rb:89:in `mktmpdir'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.11/lib/dpl/provider/pages.rb:190:in `push_app'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.11/lib/dpl/provider.rb:199:in `block in deploy'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.11/lib/dpl/cli.rb:41:in `fold'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.11/lib/dpl/provider.rb:199:in `deploy'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.11/lib/dpl/cli.rb:32:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.11/lib/dpl/cli.rb:7:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.11/bin/dpl:5:in `<top (required)>'
	from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `load'
	from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `<main>'
failed to deploy

see https://travis-ci.org/daggerok/sbt-examples/builds/546408881#L987

native-api · June 22, 2019, 9:53am

TheoLechemia · July 18, 2019, 10:28am

Hello,
I don’t know if it’s related, but I have a similar probleme with ruby with deploying. I’m using ubuntu xenial too
Here the log:

    dpl_0

    1.71s$ rvm $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl

    Successfully installed dpl-1.10.12

    1 gem installed

    dpl.1

    Installing deploy dependencies

    Successfully installed multipart-post-2.1.1

    Successfully installed faraday-0.15.4

    Successfully installed public_suffix-3.0.3

    Successfully installed addressable-2.6.0

    Successfully installed sawyer-0.8.2

    Successfully installed octokit-4.6.2

    Successfully installed dpl-pages-1.10.12

    7 gems installed

    /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/net/http.rb:906:in `rescue in block in connect': Failed to open TCP connection to http:443 (getaddrinfo: Name or service not known) (Faraday::ConnectionFailed)

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/net/http.rb:903:in `block in connect'

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/timeout.rb:93:in `block in timeout'

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/timeout.rb:103:in `timeout'

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/net/http.rb:902:in `connect'

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/net/http.rb:887:in `do_start'

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/net/http.rb:876:in `start'

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/net/http.rb:1407:in `request'

    from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/net/http.rb:1165:in `get'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:85:in `perform_request'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:43:in `block in call'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:92:in `with_net_http_connection'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:38:in `call'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/response.rb:8:in `call'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/response.rb:8:in `call'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:61:in `call'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/rack_builder.rb:143:in `build_response'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/connection.rb:387:in `run_request'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/faraday-0.15.4/lib/faraday/connection.rb:138:in `get'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/sawyer-0.8.2/lib/sawyer/agent.rb:94:in `call'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/octokit-4.6.2/lib/octokit/connection.rb:154:in `request'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/octokit-4.6.2/lib/octokit/connection.rb:19:in `get'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/octokit-4.6.2/lib/octokit/client/users.rb:34:in `user'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.12/lib/dpl/provider/pages.rb:104:in `user'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.12/lib/dpl/provider/pages.rb:108:in `setup_auth'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.12/lib/dpl/provider/pages.rb:112:in `check_auth'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/provider.rb:187:in `block in deploy'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/cli.rb:41:in `fold'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/provider.rb:186:in `deploy'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/cli.rb:32:in `run'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/cli.rb:7:in `run'

    from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/bin/dpl:5:in `<top (required)>'

    from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `load'

from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `<main>'

BanzaiMan · July 18, 2019, 12:34pm

This looks like GitHub responding with an error. You might want to retry.

lianghx-319 · July 18, 2019, 12:53pm

Deploying application
/home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.12/lib/dpl/provider/pages.rb:141:in `mkdir': File exists @ dir_s_mkdir - /tmp/d20190718-6849-1q9rxlk/work (Errno::EEXIST)
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.12/lib/dpl/provider/pages.rb:141:in `github_pull_or_init'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.12/lib/dpl/provider/pages.rb:195:in `block in push_app'
	from /home/travis/.rvm/rubies/ruby-2.4.5/lib/ruby/2.4.0/tmpdir.rb:89:in `mktmpdir'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-pages-1.10.12/lib/dpl/provider/pages.rb:190:in `push_app'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/provider.rb:199:in `block in deploy'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/cli.rb:41:in `fold'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/provider.rb:199:in `deploy'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/cli.rb:32:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/lib/dpl/cli.rb:7:in `run'
	from /home/travis/.rvm/gems/ruby-2.4.5/gems/dpl-1.10.12/bin/dpl:5:in `<top (required)>'
	from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `load'
	from /home/travis/.rvm/gems/ruby-2.4.5/bin/dpl:23:in `<main>'

dpl 1.10.12 also occur error

BanzaiMan · July 18, 2019, 1:01pm

lianghx-319 · July 19, 2019, 3:00am

Maybe user should checkout a gh-pages branch first, the ci deploy will success.
For me, it works after i pushed gh-pages to my repo

Graygzou · July 23, 2019, 5:01am

I encountered the same problem with this ruby error. But create a gh-page to solve the problem wasn’t viable in my case.

I’ve looked at the documentation and saw there is an option target_branch which is set to gh-pages by default. Setting it to master solved the problem for me.

Hope it helps !

yumetodo · July 26, 2019, 4:01am

That is exactly what I need!

target_branch must be available on the remote.

native-api · July 26, 2019, 6:39am

This would work but after the fix, it should work even without this.
If it still fails for someone, please report the new error.

domenic · July 31, 2019, 3:39pm

Just want to second that creating an empty gh-pages branch (using these instructions) and pushing it worked for me. I hope the developers can create better error messages in the future, or even better, automatically create the branch for us.

boudhayan · August 30, 2019, 5:12pm

Thanks for the help!!
the target_branch that you have specified in .travis.yml must be there in the remote.

Topic		Replies	Views
File exists @ dir_s_mkdir - Deployment build-env , bug	1	2003	June 22, 2019
Unable to deploy to github.io (dist: xenial) Deployment gh-pages	1	2359	March 11, 2019
Could not find a valid gem 'dpl-pages' Deployment gh-pages	3	1425	July 18, 2019
Getting "No such file or directory" even after file exists in the defined location during the deployment stage Deployment	4	1303	June 3, 2020
[HELP] deploy stage failes on missing `dpl/provider/releases` Linux deployment , github-releases	4	1387	September 3, 2023

"File exists @ dir_s_mkdir " ruby exception when the deploy branch doesn't exist

Related Topics