Fabien Spindler's profile - activity

I released visp for foxy and galactic using bloom-release.

I received a couple of emails from Jenkins saying that it fails in ros build farm, here for foxy, and here for galactic.

The tests that are failing require an external dataset that is not a rosbag. This dataset is packaged as a system package only for ubuntu and debian. When the system package is installed using apt-get install visp-images-data, the tests are able to find the dataset and run successfully. An other option is to clone the dataset repo and set an environment var named VISP_INPUT_IMAGE_PATH that helps to define the location of the cloned dataset when used by the tests.

1. I'm surprised to see that the buildfarm is testing the cutting edge version of ViSP available from https://github.com/lagadic/visp.git and not the last release v3.4.0 that I packaged for foxy and galactic. I must have missed something.

2. What is the best way to introduce the dataset needed by the tests ?

The solution was to ensure that tests are passing when visp dataset is not available (isolated build)

Issue disapear with the last commit

How to reproduce clang-tidy error on build farm I'm trying to fix the following build farm issue during visp packaging f

visp foxy and galactic release fails on ros 2 buildfarm I released visp for foxy and galactic using bloom-release. I re

visp foxy and galactic release fails on ros 2 buildfarm I released visp for foxy and galactic using bloom-release. I re

The tracker_type param could be set to:

• mbt: meaning tracking with edges only
• klt: tracking with keypoints only
• mbt+klt: hybrid tracking using edges + keypoints

`

<node pkg="visp_tracker" type="tracker" name="tracker_mbt">
    <param name="camera_prefix" value="/wide_left/camera" />
    <param name="tracker_type" value="mbt+klt" />
</node>

When I release visp ( https://github.com/lagadic/visp-release ) for jade or indigo with

$ bloom-release --rosdistro jade --track jade visp

I see the package in the default repo http://repositories.ros.org/status_pa... but NOT in the arm repo http://repositories.ros.org/status_pa...

When I release for kinetic the package seems available for default and arm ( http://repositories.ros.org/status_pa... and http://repositories.ros.org/status_pa... ).

Why is it not the case for indigo and jade ?

Hi,

I can't understand what is wrong when I try to release with bloom:

In my repo https://github.com/lagadic/vision_visp I have done for groovy branch:

$ catkin_generate_changelog
$ catkin_tag_changelog
$ catkin_prepare_release

that has created the new tag groovy-0.7.4

Then to release this new version to https://github.com/lagadic/vision_vis... I did:

$ bloom-release vision_visp --track groovy --rosdistro groovy
...
Everything up-to-date
==> Releasing 'vision_visp' using release track 'groovy'
==> git-bloom-release groovy
Processing release track settings for 'groovy'
Checking upstream devel branch for package.xml(s)
Cloning into '/tmp/tmpePvEhb/upstream'...
remote: Reusing existing pack: 3388, done.
remote: Counting objects: 191, done.
remote: Compressing objects: 100% (191/191), done.
remote: Total 3579 (delta 119), reused 3 (delta 0)
Receiving objects: 100% (3579/3579), 1.35 MiB | 527.00 KiB/s, done.
Resolving deltas: 100% (2161/2161), done.
Checking connectivity... done.
Looking for packages in 'groovy' branch... found 6 packages.
Detected version '0.7.4' from package(s): ['visp_camera_calibration', 'visp_hand2eye_calibration', 'vision_visp', 'visp_auto_tracker', 'visp_tracker', 'visp_bridge']

Executing release track 'groovy'
==> bloom-export-upstream /tmp/tmpePvEhb/upstream git --tag groovy-0.7.4 --display-uri https://github.com/lagadic/vision_visp.git --name upstream --output-dir /tmp/tmpruKz1m
Checking out repository at 'https://github.com/lagadic/vision_visp.git' to reference 'groovy-0.7.4'.
Exporting to archive: '/tmp/tmpruKz1m/upstream-groovy-0.7.4.tar.gz'
md5: 746ef2c87d8cd72fc7031992d6e05604

==> git-bloom-import-upstream /tmp/tmpruKz1m/upstream-groovy-0.7.4.tar.gz  --release-version 0.7.4 --replace
The latest upstream tag in the release repository is 'upstream/0.7.3'.
Importing archive into upstream branch...
The package(s) in upstream are version '0.7.3', but the version to be released is '0.7.4', aborting.
<== Error running command '['/usr/bin/git-bloom-import-upstream', '/tmp/tmpruKz1m/upstream-groovy-0.7.4.tar.gz', '--release-version', '0.7.4', '--replace']'
Release failed, exiting.

Many thanks if you have some ideas ?

Best regards

Fabien

I wanted that the following class protected by an #ifdef appears in the generated class list:

#ifdef HAVE_MY_LIBRARY
class myClass {
public;
  myClass(){};
};
#endif

With doxygen this could be achieved by putting PREDEFINED="HAVE_MY_LIBRARY" in the config file.

I haven't see how to do the same with rosdoc_lite ?

Regards Fabien

I'm not able to reproduce your error on ubuntu 12.04 x64 with groovy. Prior my attempt, I have updated the package list: $ sudo apt-get update $ sudo apt-get install ros-groovy-visp $ sudo apt-cache depends libfreenect-dev libfreenect-dev Depends: libusb-1.0-0-dev Depends: libfreenect0.0 Conflicts: libfreenect-dev:i386

What is your Ubuntu distro ?

As Thomas said, the build options used to generate ViSP library are not compatible with ROS usage. May be you install ViSP as a static library, or if it is a dynamic one, it was not built with -fPIC. This is typically the case if you have installed ViSP as indicated in http://www.irisa.fr/lagadic/visp/install-sdk.html#ubuntu-12 Just to complete Thomas answer, to be sure that you have removed all existing version of ViSP you can use locate: $ sudo updatedb $ locate libvisp $ locate VISPConfig.cmake The two last command should return an empty answer. If this is the case, you can enter step 3 mentioned by Thomas.

I'm porting visp to indigo. According to http://www.ros.org/debbuild/indigo.ht... it fails for trusty with the followin error (see http://jenkins.ros.org/view/IbinT32/j... ):

package ros-indigo-visp does not have dependency [ffmpeg]
Dependencies not satisfied for packages: ['ffmpeg']
Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information
Build step 'Execute shell' marked build as failure
Build step 'Groovy Postbuild' marked build as failure
Build step 'Groovy Postbuild' marked build as failure

In https://github.com/ros/rosdistro/blob... , ffmpeg dependency is now specific for trusty. We have:

ffmpeg:
  ubuntu:
     trusty: [libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev]

I can't understand wy I get this error "Dependencies not satisfied for packages: ['ffmpeg']". It should not happen as ffmpeg is not a dep for trusty. I'm wrong. Is there a problem with the build farm.

Moreover I'm also surprised with the last lines of the log:

Build step 'Groovy Postbuild' marked build as failure

The build is for indigo. Wy does it mention groovy ?

My project depends on libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev. To this end for groovy and hydro in package.xml I added a build and run dependency on ffmpeg that brings from rosdep the expected dependencies:

In https://github.com/ros/rosdistro/blob... there is:

ffmpeg:
  arch: [ffmpeg]
  debian: [ffmpeg, libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev]
  fedora: [ffmpeg-devel]
  gentoo:
    portage:
      packages: [media-plugins/ffmpeg]
  macports: [ffmpeg]
  ubuntu: [ffmpeg, libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev]

Now for indigo it seems that the ffmpeg debian package is not available for trusty.

We cannot change rosdep/base.yaml to the following (even if it shall work for trusty):

  debian: [libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev]
  ubuntu: [libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev]

Shall I introduce new entries for each debian package ?

libavcodec-dev:
  debian: [libavcodec-dev]
  ubuntu: [libavcodec-dev]

libavformat-dev:
  debian: [libavformat-dev]
  ubuntu: [libavformat-dev]

libavutil-dev:
  debian: [libavutil-dev]
  ubuntu: [libavutil-dev]

libswscale-dev:
  debian: [libswscale-dev]
  ubuntu: [libswscale-dev]

Any ideas ? Thanks

Fabien

As explained on the tutorial http://www.ros.org/wiki/visp_camera_calibration/Tutorials/CalibrationExperimentalCamera, the calibration.ini file should be in your $HOME/.ros directory

Fabien