Not currently with the web UI, but you can do this with the CLI tool. Something like (use "-help" if this doesn't work out of the box):

$ cit logdog cat chromiumos/bb/.../stdout > /path/to/file.txt

Is cit a commonly used tool? I don't think I ever heard about it. Does not seem to work in the following attempts:

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

$ cit logdog cat https://logs.chromium.org/v/?s=chromiumos%2Fbb%2Fchromiumos%2Foak-full%2F7598%2F%2B%2Frecipes%2Fsteps%2FUnitTest%2F0%2Fstdout
Unknown tool "logdog"
usage: cit.py <name of tool> [args for tool]
...
$ cit log --help
You must use the virtualenv in ENV for scripts in the infra repo.
Running `gclient runhooks` will create this environment for you.
$ gclient runhooks
In the chroot, it is a bad idea to run gclient runhooks
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

it would be great to see some exact instructions on how to get a log into a text file.

Interesting - "cit logdog" is the command to use. Is it possible that you have a *really* old "depot_tools" checkout?

The "cit" tool in "depot_tools" is a gateway tool to a lot of Chrome Operations tooling ("cit" => "Chrome Infrastructure Tool"). It really is just a passthrough to download+run the named tool. That said, "logdog" has been integrated into it for at least half a year.

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
$ repo --version
repo version v1.12.37-cr1
       (from https://chromium.googlesource.com/external/repo.git)
repo launcher version 1.23
       (from /mnt/host/depot_tools/repo)
git version 2.13.5
Python 2.7.10 (default, Aug  9 2017, 13:19:48) 
[GCC 4.2.1 Compatible Chromium OS 5.0_pre300080-r12 Clang 5.0.0 (/var/cache/chr


in the repo git tree:
$ git log -n 1
commit a3a80b69082f413a6849c979b35dad0e69cb9d48
Author: Corentin Wallez <cwallez@chromium.org>
Date:   Wed Mar 14 14:16:04 2018 -0400

    presubmit_unittest.py: use LUCI for the optional GPU tests on Linux


Author: Corentin Wallez <cwallez@chromium.org>
Date:   Wed Mar 14 14:16:04 2018 -0400
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

does not seem very old, is this the correct repo:

remote.origin.url=https://chromium.googlesource.com/chromium/tools/depot_tools.git

You may need to run "gclient runhooks" in your "depot_tools" directory. "cit" only knows how to bootstrap available files, and the "logdog" binary is only available when the "update_depot_tools" hook has executed. The easiest way to run this hook is to just run the "gclient" command from your "depot_tools" directory.

$ /path/to/depot_tools/gclient

Since you're using "repo", I assume this is a ChromeOS checkout. I'm not sure how CrOS' toolchain checks out "depot_tools", but it's possible that they aren't running the "gclient" command/hook after it is checked out.

yes, this is a Chrome OS checkout, this is what I get when trying

'gclient repohooks'

$ ./gclient runhooks
Error: client not configured; see 'gclient config'


I am a bit apprehensive of all these complications - there have been no need to do any for that for Chrome OS.

I didn't say "gclient runhooks"; I said "gclient" :) The act of getting that error message may have downloaded the tool. Try again?

These complications are not so prominent in Chromium development, since "gclient" is run regularly against their "depot_tools", causing this tooling to be enabled by default. Once we get you working, the follow-up action item will be for you to file a bug against CrOS infrastructure to make the "cit logdog" (and other "cit" tools) available in their "depot_tools" "repo" checkout.

ok, it worked after all outside of chroot.

a bit cumbersome - url needs to be cleaned up by hand. Sure is better than nothing, but being able to save a log in a text file directly from web interface would be much more convenient...

Glad to hear it. Please follow up with the action item that I suggested in #7 and file a bug against CrOS infrastructure to make Chrome Operations "depot_tools" tooling more accessible to CrOS developers.

RE your other comments, you may be interested in:
- https://bugs.chromium.org/p/chromium/issues/detail?id=705015
- https://bugs.chromium.org/p/chromium/issues/detail?id=809326
- https://bugs.chromium.org/p/chromium/issues/detail?id=793882

These aren't new ideas, but they haven't yet been prioritized.

Closing, as I believe this is resolved. vbendeb@, since you don't seem to have created an issue with CrOS infrastructure, I have gone ahead and done so: crbug.com/831131

Please don't drop this sort of thing - if we don't follow-up on issues, we'll never get them resolved in a permanent and satisfactory manner.