Some test failures include the process id. For example, "Chrome login failed: OOBE target not found: browser process 16943 replaced by 16944; Chrome probably crashed." Looking at the stainless report I do not see any logs with 16944 in the name. Only by clicking on each of the logs and looking for the PID was I able to correlate chrome_20190110-144503 with PID 16944.

Even more useful would be if the logs were grouped under the failing test. For example, in this case "ui.MashLogin' failed, yet I have to click around the chrome/ui logs to figure out which one it corresponded to.

Here's the stainless report: https://stainless.corp.google.com/browse/chromeos-autotest-results/275721946-chromeos-test/ . And failing test is "ui.MashLogin".