Closed hsd-dev closed 5 years ago
Looks like git
can't find commit ca7b5363
in the clone of robust-rosin/cob_control
.
It does exist though: https://github.com/robust-rosin/cob_control/commit/ca7b536390bcf76bf4ab6e62354c52bd51fb1ece.
@ChrisTimperley: would you have any idea? Could this be related to this: https://github.com/robust-rosin/robust/blob/9c5e6997378b8f83e2758abd80acb265ece3dabd/Dockerfile#L39-L54
@ipa-hsd: could you please push your changes to the .bug
file to a care-o-bot/ca7b536
branch?
Interesting. I'm able to reproduce your build failure via BugZoo, and by running the same Git commands natively on my machine:
chris@nostromo:~$ cd /tmp/
chris@nostromo:/tmp$ git clone https://github.com/robust-rosin/cob_control
Cloning into 'cob_control'...
remote: Enumerating objects: 13805, done.
remote: Total 13805 (delta 0), reused 0 (delta 0), pack-reused 13805
Receiving objects: 100% (13805/13805), 5.71 MiB | 11.37 MiB/s, done.
Resolving deltas: 100% (8849/8849), done.
chris@nostromo:/tmp$ cd cob_control/
chris@nostromo:/tmp/cob_control$ git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*"
chris@nostromo:/tmp/cob_control$ git fetch --all
Fetching origin
chris@nostromo:/tmp/cob_control$ git diff f596e45f4fd43ea2d696e32c966314e107aee84a ca7b536390bcf76bf4ab6e62354c52bd51fb1ece
fatal: bad object ca7b536390bcf76bf4ab6e62354c52bd51fb1ece
Looking at the associated PR, there's a lot of force pushing going on: https://github.com/ipa320/cob_control/pull/47
Yes. Indeed.
Wouldn't https://github.com/ipa320/cob_control/commit/9dac57a1a6f4c9edddd2125c5f8b9409526a26bf be the correct commit for fix
?
Or otherwise https://github.com/ipa320/cob_control/pull/47/commits/47adcee14c7f39645352f2226b32c5f116ea0c22?
But it's probably better to use the merge commit so we can assume things are in a consistent state.
Thanks for your inputs on Wednesday. I am able to build the image with ipa320/cob_control@47adcee
While running the
rosinstall-generator
with the following command:I get the error that
cob_obstacle_distance
is not released at the time the bug was reported:So I added the
datetime
tag totime-machine
:which is 1 day after the package was released. After that I was able to generate the
deps.rosinstall
file.Now I notice that in
robust.bugzoo.yml
, there are 2 images for each bug::bug
and:fix
. Guess it is from here: https://github.com/robust-rosin/robust/commit/ecc6facfb816b91979904e377f7e9e19c41a2e96Do I build these 2 images separately? What happens to the ones I have already built for previous bugs, should I rebuild them all?
Also while building the bugzoo images:
I get the following error: