Closed git-afsantos closed 4 years ago
For reference, the problematic bug is robust:5ee65b0.
It's fine to use cpp
as a workaround for now. The only area where language has any influence is on the generation of coverage information, which isn't currently supported for Python programs. I'll get BugZoo to report a reasonable error message to the terminal. Do you mind sharing the complete command that you passed to BugZoo so that I can quickly test a fix? :)
It's fine to use cpp as a workaround for now.
Alright. Will try that.
I just ran bugzoo source update
, after having already a local repository registered as a source.
And here is the manifest I was trying to add, if it matters.
version: '1.0'
blueprints:
- type: docker
tag: robustrosin/robust:5ee65b0
file: ../../Dockerfile
arguments:
IS_BUILD_FAILURE: "no"
USE_APT_OLD_RELEASES: "no"
UBUNTU_VERSION: trusty
ROS_DISTRO: indigo
CATKIN_PKG: kobuki_dashboard
REPO_FORK_URL: https://github.com/robust-rosin/kobuki_desktop
REPO_BUG_COMMIT: 37a1eee5ce2642144735102ffcd4c3736c4b2850
REPO_FIX_COMMIT: d852bd6dbc24c7096bd6f042739725b894359494
bugs:
- name: robust:5ee65b0
image: robustrosin/robust:5ee65b0
program: kobuki_dashboard
dataset: robust
languages:
- python
source-location: /ros_ws/src
test-harness:
type: empty
compiler:
type: catkin
workspace: /ros_ws/src
time-limit: 300
When trying to build a
.bugzoo.yml
file for a bug with languagepython
(orpy
), and then runningbugzoo source update
, the command fails.No errors are printed to the console, but the log file contains the following error.
Is it safe to use
cpp
as a workaround, or does it influence the outcome?