-
Right now we have a single `.bugzoo.yml` per repository / program.
I'm wondering if it would be ok to have one per bug.
If that is ok (for BugZoo as well as us humans), then I think I can automa…
-
Ran into this:
```
error: Could not find suitable distribution for Requirement.parse('Werkzeug>=0.7')
```
fixed it with
```
joe@b120ba:~/BugZoo$ pip3 install -U Werkzeug
```
Then was able …
-
Attempting "bugzoo bug build" on any of the manybugs benchmark bugs results in a failure with the following error message:
**wget: unable to resolve host address 'repairbenchmarks.cs.umass.edu'
..…
-
-
We'll need to
- [x] rename the current forks (as they now have a bug id as part of their name)
- [x] add `REPO_FIX_COMMIT` and `REPO_BUG_COMMIT` to `Dockerfile`
- [x] update `switch` to use th…
-
I like isolation.
Instead of installing to `--user`, perhaps we should recommend users create a virtualenv and install bugzoo there?
-
The first time I try to use bugzoo so please forgive fumbling:
```
ros@Gorce:~/work/robust$ bugzoo bug build robust:eed104d
building bug: robust:eed104d
Building image: rosin/robust:eed104d
Ste…
-
The tf2 bugs are now in tf2/ and the yml file is tf2.bugzoo.yml. It is slightly confusing, as the repository name is geometry2. Shoudl we name all collections after the original repository names? so…
-
```
bugzoo container launch robust:b4dc23c
root@dbddb1fd7820:/ros_ws# rospack help find tf2_ros
[rospack] Error: package 'tf2_ros' not found
root@4b7bb14578f8:/ros_ws# source devel/setup.sh
root…
-
Not sure what is going on, just logging this for now.
While building an image for `f8d175b` (universal_robot), I see the following in the build log:
```
-- Installing: /opt/ros/lib/pkgconfig/tf…