#582 Use different status based on reason for failure
Opened 7 years ago by lsedlar. Modified 7 years ago

Currently if the compose fails for any reason the final status is always DOOMED. This makes it difficult for gathering metrics, because the failure could be a problem in the package set, or it could be a bug in pungi.

It would be nice to have a separate status to distinguish between these two failure situations. I'm thinking BROKEN_PKGSET, but any better name is welcome.

As a beginning we should use this status in these situations:

  • when there are broken dependencies (and check_deps=True) – this is a clear case with no false positives
  • when a koji task fails – this could in theory be false positive because there might be an authentication problem, or maybe a bug in calling the command (maybe there is a reasonable way to tell these apart)

Login to comment on this ticket.

Metadata