#69 copr-builder does not clean state after build
Closed 6 years ago Opened 7 years ago by clime.

Hello, if I run several builds in the same project and in the same chroot (not sure if this is necessary), then instead of actual building, the build results of the previous build are discovered and immediately copied to backend.


There's:

````
261 /var/lib/copr-builder/results)
262     # We know that it is safe to remove everything from here.
263     rm -rf "$opt_resultdir"
264     mkdir "$opt_resultdir"
265     ;;
```

If I run several builds in the same project and in the same chroot

What are the exact steps to reproduce this?

Metadata Update from @praiskup:
- Issue assigned to praiskup

7 years ago

Ping. Using copr-builder internally in production for a while I'm not able to reproduce. Perhaps we could close this?

IMO copr-builder cleans the resultdir (copr-rpmbuild does not). Considering this notabug, then.

Metadata Update from @praiskup:
- Issue status updated to: Closed (was: Open)

6 years ago

Log in to comment on this ticket.

Metadata