Commit Graph

10 Commits

Author SHA1 Message Date
Michael Hudson-Doyle 683d1932ac have replayed curtin runs create a log file too 2019-11-21 14:55:23 +13:00
Michael Hudson-Doyle e8a9cdf4f8 have dry-run install failures replay events from a real failure 2019-11-21 11:25:43 +13:00
Michael Hudson-Doyle ca02972195 add a controlled way to make various things fail
In dry-run mode, treat SUBIQUITY_DEBUG as a comma-separated list of
things to fail:

 * install-fail: curtin install fails
 * copy-logs-fail: the postinstall copying of logs fails
 * bpfail-full: full block device probing fails
 * bpfail-restricted: restricted block device probing fails

In addition, control-u makes the UI crash in dry-run mode.

(This is all for testing of crash report generation but does not depend
on that).
2019-11-04 10:43:29 +13:00
Michael Hudson-Doyle b77aa9499e make sure all delays during replaying answers repsect SUBIQUITY_REPLAY_TIMESCALE 2019-02-21 11:07:54 +01:00
Michael Hudson-Doyle 6b156766bb change replay-curtin-log to give a more realistic experience in dry-run mode 2018-02-28 15:57:35 +13:00
Michael Hudson-Doyle ef0632175b use a different syslog identifier for each subiquity process 2018-02-28 13:49:24 +13:00
Michael Hudson-Doyle 05c5f4218a make log replay timescale adjustable
want to be able to slow it down when hacking on the log view!
2018-02-12 14:44:40 +13:00
Michael Hudson-Doyle 1a939844fb use the journald event reporter that is now part of curtin 2018-02-12 13:37:00 +13:00
Michael Hudson-Doyle 2779bac01a change the log replayer to be more realistic 2018-02-12 13:30:00 +13:00
Michael Hudson-Doyle d756596093 hook up curtin's event reporting into journald and watch these messages during install 2017-09-18 22:50:00 +12:00