Open zmichaels11 opened 4 years ago
A release is simultaneously being pushed to pip
and apt
(which apt even being delayed a bit until new packages are imported from the bootstrap repo into building/testing/main and then later synced to the official mirror). So switching from pip
to apt
will pick up new changes not earlier but even later.
I'm suggesting testing against both not switching. The purpose of this feature request is to help detect if the reason why colcon-bundle
is failing is due to changes in colcon
by providing a comparison against a more stable release.
against a more stable release
I am not understanding where the "more stable release" is coming from? The apt repo only contains the latest release. From pip
you could install older versions (but it would be hard to know what older version to try).
Description
The recent build failures on
colcon-bundle
were due to upstream breaking changes applied tocolcon-python-setup-py
. TheAPT
installation ofcolcon
is considered the stable installation. To help quicken triaging broken builds ofcolcon-bundle
, tests should be added that runcolcon-bundle
's tests usingAPT
installedcolcon
instead of PIP.Exit Criteria
APT
installedcolcon
. This should run on both PR and periodically, however it should not qualify for paging @ros2/aws-oncall at this time.