Commit 304d0f5c authored by Harald Sitter's avatar Harald Sitter

enable ttyS1 logging for livetests

it appears time and again that the livetests get weirdly stuck on reboot
into the final system. we have next to no useful data at that point in time
and I have that ttyS1 logging will help us there
parent 5f89eac6
......@@ -20,6 +20,7 @@
# Hook run at the earlierst possiblity. Should generally not fail but do stuff
# which must happen ASAP.
# NB: this is also run for all livetests, so be careful with what is done here.
puts "#{$0}: Running early first start hook..."
......
......@@ -223,6 +223,13 @@ sub boot {
assert_script_run 'wget ' . data_url('permissions_check.rb'), 16;
assert_script_run 'ruby permissions_check.rb', 16;
# This primarily makes sure apt isn't hogged by apt-daily AND most
# importantly sets up a journald console output for /dev/ttyS1.
# This script will also be run for the final system on first start and
# retained in the image.
assert_script_run 'wget ' . data_url('early_first_start.rb'), 16;
assert_script_sudo 'ruby early_first_start.rb', 60 * 5;
# TODO: maybe control via env var?
# assert_script_run 'wget ' . data_url('enable_qdebug.rb'), 16;
# assert_script_run 'ruby enable_qdebug.rb', 16;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment