veyepar: Modernising firmware testing on POWER with Python and pre-release everything

Author(s):	Stewart Smith
Location	Collaborative Lecture Theatre CB11.00.405
Date	jan Fri 26	Days Raw Files
Start	11:40	First Raw Start	11:19
Duration	0:45:0	Offset	0:20:26
End	12:25	Last Raw End	12:49
Chapters	00:00 0:09:29 0:32:45 0:39:28 0:41:01
Total cuts_time	45 min.

http://lca2018.linux.org.au/schedule/presentation/87/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive public tweet mp4 svg png

assets release.pdf Modernising_firmware_testing_on_POWER_with_Python_and_prerelease_everything.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Some people have the odd expectation that they will be able to (reliably) turn their computers on and off. On top of that, other people seem to have the entirely unreasonable expectation to have their computers reliably boot an Operating System, perform consistently, and not catch fire. In order to meet these outrageous expectations, we need to test firmware before we release it to an unsuspecting public. After all, isn't the gold standard of testing "if it boots, ship it" ? In the era of Blockchain, the gold standard no longer applies. As a firmware maintainer, I want the answer to a simple question: "Will I regret merging this code?". A simple and quick automated test suite is in order! Unfortunately, such things are not always around when you need them. In order to successfully deliver POWER9 systems (new processor, new operating systems, new machines, new BMC software), we would need a high quality, reliable, fast, easy to use, automated firmware test suite that could not only spot regressions, but find new bugs. This is a tale of code and organizational transformation and discovery during an incredibly tight and largely immobile release schedule. We'll cover: - Components of a modern POWER server and how one might test them (on purpose or by accident) - Practical use of Python in a mix of modern and legacy environments without going insane - (ab)using existing testing frameworks for (almost) fun and (hopefully) profit - How to (not) live with old enterprise distros - Transforming development, test, and management organizations, into test focused ones. - How on earth do you design a firmware compliance test before you have a test suite anyway? This talk is brought to you by: - A Perl script calling a perl script that parses XML with regex that ran a shell script to construct a python script to shell out to expect. - Unexpected bugs in the TTY layer - Soft Lockups - SOL Disconnected by BMC. markdown
Comment:	production notes