ab0a8057bf
When osbuild crashes (e.g. when cp fails because of the machine running out of disk space), it doesn't produce a machine-readable result. Due to our suboptimal handling of the result struct (this is my fault), this can lead to result == nil. However, composer expects that result != nil in all cases because it uses the Success flag to assess the compose state. If result == nil, it just crashes terribly. |
||
|---|---|---|
| .. | ||
| osbuild-composer | ||
| osbuild-dnf-json-tests | ||
| osbuild-image-tests | ||
| osbuild-koji | ||
| osbuild-pipeline | ||
| osbuild-rcm-tests | ||
| osbuild-store-dump | ||
| osbuild-tests | ||
| osbuild-upload-aws | ||
| osbuild-upload-azure | ||
| osbuild-worker | ||