fd46679eae
Sometimes aptly can't process an DEB upload request from build-pkgs. This may happen for example, if aptly's disk is full or its database is corrupted. Currently buildp-pkgs just assumes that an upload always succeeds and ignores any errors. This may result in incomplete, but seemingly successful runs of build-pkgs. Solution: raise an exception if upload fails (ie exit immediately with a stack trace). TESTS ============================ * Call build-pkgs and manually pause aptly with SIGSTOP just before build-pkgs attempts to upload its first package. Make sure we get a "timed out" exception and exit with non-zero status. * Same test for a specific package, rather than all, ie build-pkgs -p build-info * Build all packages normally Signed-off-by: Davlet Panech <davlet.panech@windriver.com> Change-Id: I6be26370def68ea00b4983d5d148285797a18b54