Ask Your Question

Revision history [back]

Build failure after moving submodule

In the enu package. The initial release had an error related to headers, which I'm hoping I've resolved, but in the process of getting there, I moved a submodule within the package, which seems to triggered an issue with a git rebase operation:

$ bloom-release --track hydro --ros-distro hydro enu
==> Fetching 'enu' repository from 'https://github.com/clearpath-gbp/enu-release.git'
Cloning into '/tmp/tmpHts1LF'...
remote: Counting objects: 125, done.
remote: Compressing objects: 100% (82/82), done.
remote: Total 125 (delta 28), reused 122 (delta 27)
Receiving objects: 100% (125/125), 22.07 KiB, done.
Resolving deltas: 100% (28/28), done.
==> Setting release repository remote url to 'https://github.com/clearpath-gbp/enu-release.git'
==> git remote set-url origin https://github.com/clearpath-gbp/enu-release.git
==> Testing for push permission on release repository
==> git remote -v
origin  https://github.com/clearpath-gbp/enu-release.git (fetch)
origin  https://github.com/clearpath-gbp/enu-release.git (push)
==> git push --dry-run
Everything up-to-date
==> Releasing 'enu' using release track 'hydro'
==> git-bloom-release hydro
Processing release track settings for 'hydro'
Checking upstream devel branch for package.xml(s)
Cloning into '/tmp/tmpWfQzCL/upstream'...
remote: Counting objects: 183, done.
remote: Compressing objects: 100% (83/83), done.
remote: Total 183 (delta 86), reused 177 (delta 82)
Receiving objects: 100% (183/183), 30.35 KiB, done.
Resolving deltas: 100% (86/86), done.
Submodule 'libswiftnav' (https://github.com/swift-nav/libswiftnav.git) registered for path 'libswiftnav'

Cloning into 'libswiftnav'...

Submodule path 'libswiftnav': checked out '8ab443d2c801480958b434d9f179e57c916f9f4f'

Looking for packages in 'hydro' branch... found 'enu'.
Detected version '1.0.2' from package(s): ['enu']

Executing release track 'hydro'
==> bloom-export-upstream /tmp/tmpWfQzCL/upstream git --tag 1.0.2 --display-uri https://github.com/clearpathrobotics/enu.git --name enu --output-dir /tmp/tmpIG1vfW
Checking out repository at 'https://github.com/clearpathrobotics/enu.git' to reference '1.0.2'.
Exporting to archive: '/tmp/tmpIG1vfW/enu-1.0.2.tar.gz'
md5: 134e1a7b9d8b4533fc6d94188541a6bf

==> git-bloom-import-upstream /tmp/tmpIG1vfW/enu-1.0.2.tar.gz  --release-version 1.0.2 --replace
The latest upstream tag in the release repository is 'upstream/1.0.1'.
Importing archive into upstream branch...
Creating tag: 'upstream/1.0.2'
Im happy.  You should be too.

==> git-bloom-generate -y rosrelease hydro --source upstream -i 0
Releasing package: ['enu']
Releasing package 'enu' for 'hydro' to: 'release/hydro/enu'
 [git-bloom-patch rebase]: 'execute_command' failed to call 'git rm -rf *' which had a return code (128):
 [git-bloom-patch rebase]: ```
fatal: pathspec 'libswiftnav' did not match any files

 [git-bloom-patch rebase]: ```
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/bloom/commands/git/generate.py", line 101, in try_execute
    retcode = func(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/bloom/logging.py", line 210, in decorated
    return f(*args, **kwds)
  File "/usr/lib/pymodules/python2.7/bloom/commands/git/patch/rebase_cmd.py", line 146, in rebase_patches
    non_git_rebase(config['parent'], directory=directory)
  File "/usr/lib/pymodules/python2.7/bloom/commands/git/patch/rebase_cmd.py", line 42, in non_git_rebase
    execute_command('git rm -rf *', cwd=directory)
  File "/usr/lib/pymodules/python2.7/bloom/util.py", line 388, in execute_command
    raise CalledProcessError(result, cmd)
CalledProcessError: Command 'git rm -rf *' returned non-zero exit status 128

Error calling git-bloom-patch rebase: Command 'git rm -rf *' returned non-zero exit status 128
git-bloom-patch rebase returned exit code (128)
<== Error running command '['/usr/bin/git-bloom-generate', '-y', 'rosrelease', 'hydro', '--source', 'upstream', '-i', '0']'
Release failed, exiting.

Anyone know what happened here? Is there a quick fix possible?

Build failure after moving submodule

In the enu enu package. The initial release had an error related to headers, which I'm hoping I've resolved, but in the process of getting there, I moved a submodule within the package, which seems to triggered an issue with a git rebase operation:

$ bloom-release --track hydro --ros-distro hydro enu
==> Fetching 'enu' repository from 'https://github.com/clearpath-gbp/enu-release.git'
Cloning into '/tmp/tmpHts1LF'...
remote: Counting objects: 125, done.
remote: Compressing objects: 100% (82/82), done.
remote: Total 125 (delta 28), reused 122 (delta 27)
Receiving objects: 100% (125/125), 22.07 KiB, done.
Resolving deltas: 100% (28/28), done.
==> Setting release repository remote url to 'https://github.com/clearpath-gbp/enu-release.git'
==> git remote set-url origin https://github.com/clearpath-gbp/enu-release.git
==> Testing for push permission on release repository
==> git remote -v
origin  https://github.com/clearpath-gbp/enu-release.git (fetch)
origin  https://github.com/clearpath-gbp/enu-release.git (push)
==> git push --dry-run
Everything up-to-date
==> Releasing 'enu' using release track 'hydro'
==> git-bloom-release hydro
Processing release track settings for 'hydro'
Checking upstream devel branch for package.xml(s)
Cloning into '/tmp/tmpWfQzCL/upstream'...
remote: Counting objects: 183, done.
remote: Compressing objects: 100% (83/83), done.
remote: Total 183 (delta 86), reused 177 (delta 82)
Receiving objects: 100% (183/183), 30.35 KiB, done.
Resolving deltas: 100% (86/86), done.
Submodule 'libswiftnav' (https://github.com/swift-nav/libswiftnav.git) registered for path 'libswiftnav'

Cloning into 'libswiftnav'...

Submodule path 'libswiftnav': checked out '8ab443d2c801480958b434d9f179e57c916f9f4f'

Looking for packages in 'hydro' branch... found 'enu'.
Detected version '1.0.2' from package(s): ['enu']

Executing release track 'hydro'
==> bloom-export-upstream /tmp/tmpWfQzCL/upstream git --tag 1.0.2 --display-uri https://github.com/clearpathrobotics/enu.git --name enu --output-dir /tmp/tmpIG1vfW
Checking out repository at 'https://github.com/clearpathrobotics/enu.git' to reference '1.0.2'.
Exporting to archive: '/tmp/tmpIG1vfW/enu-1.0.2.tar.gz'
md5: 134e1a7b9d8b4533fc6d94188541a6bf

==> git-bloom-import-upstream /tmp/tmpIG1vfW/enu-1.0.2.tar.gz  --release-version 1.0.2 --replace
The latest upstream tag in the release repository is 'upstream/1.0.1'.
Importing archive into upstream branch...
Creating tag: 'upstream/1.0.2'
Im happy.  You should be too.

==> git-bloom-generate -y rosrelease hydro --source upstream -i 0
Releasing package: ['enu']
Releasing package 'enu' for 'hydro' to: 'release/hydro/enu'
 [git-bloom-patch rebase]: 'execute_command' failed to call 'git rm -rf *' which had a return code (128):
 [git-bloom-patch rebase]: ```
fatal: pathspec 'libswiftnav' did not match any files

 [git-bloom-patch rebase]: ```
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/bloom/commands/git/generate.py", line 101, in try_execute
    retcode = func(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/bloom/logging.py", line 210, in decorated
    return f(*args, **kwds)
  File "/usr/lib/pymodules/python2.7/bloom/commands/git/patch/rebase_cmd.py", line 146, in rebase_patches
    non_git_rebase(config['parent'], directory=directory)
  File "/usr/lib/pymodules/python2.7/bloom/commands/git/patch/rebase_cmd.py", line 42, in non_git_rebase
    execute_command('git rm -rf *', cwd=directory)
  File "/usr/lib/pymodules/python2.7/bloom/util.py", line 388, in execute_command
    raise CalledProcessError(result, cmd)
CalledProcessError: Command 'git rm -rf *' returned non-zero exit status 128

Error calling git-bloom-patch rebase: Command 'git rm -rf *' returned non-zero exit status 128
git-bloom-patch rebase returned exit code (128)
<== Error running command '['/usr/bin/git-bloom-generate', '-y', 'rosrelease', 'hydro', '--source', 'upstream', '-i', '0']'
Release failed, exiting.

Anyone know what happened here? Is there a quick fix possible?