I tried to reproduce the failure Ryan described (malformed sources file), but couldn't.
On handling an install failure (subiquity crash): I think that failing in a clear way is better than retrying in an unclear way. Testing the retry-after-failure path is quite difficult as real world failure modes are unexpected, by definition we could say. IMHO on a crash it could make sense for subiquity to allow the user to:
- submit logs
- jump to a shell to inspect the failure
- reboot the system
without allowing the user to retry the install without rebooting.
I tried to reproduce the failure Ryan described (malformed sources file), but couldn't.
On handling an install failure (subiquity crash): I think that failing in a clear way is better than retrying in an unclear way. Testing the retry-after-failure path is quite difficult as real world failure modes are unexpected, by definition we could say. IMHO on a crash it could make sense for subiquity to allow the user to:
- submit logs
- jump to a shell to inspect the failure
- reboot the system
without allowing the user to retry the install without rebooting.