| Age | Commit message (Collapse) | Author |
|---|
|
A typical invocation logging would also include a value
for "--dump-artifacts". Mention this in the tutorial.
|
|
... as this also works together with, e.g., linting. While there,
also rerun the examples to get the latest output messages.
|
|
|
|
|
|
|
|
|
|
|
|
Normally, actions are supposed to work silently, i.e., without writing
to stdout/stderr. So, if an action produces console output, it is
definitely worth looking at, even for cached actions. Therefore,
add a section after the failed actions showing those actions (if
not in the previous action). Also, always show duration (if known)
and if an action is cached (which can happen for the ones producing
console output).
|
|
When using a serve endpoint, analysis errors my contain a reference to
a build failure on serve, shown as 'blob <hash>'. For each such blob
reference add a link offering to read this blob.
|
|
Currently the support hashes are SHA-1 (for git hashes), which has 160 bits and
SHA-256 which has 256 bits. Therefore, we expect either 40 or 64 hex digits.
|
|
|
|
|
|
|
|
|
|
While there, sort filter URLs
|
|
|
|
to 100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The directory name is designed to allow an easy rough sorting by
time. This can also be used to identify the latest build for a
specific user. However, users often run several builds in a single
minute; therefore, increase time-stamp precission to include
seconds as well. While still lexicographic and chronological order
will disagree, at least for a single user it will be correct most
of the times.
|
|
When looking at an invocation, it can be helpful to quickly get
all other invocation that coincide with a specific remote-execution
property (like the build image). Support this use case by adding
appropriate filtering and links.
|
|
|
|
Include in the profile also the effective remote-execution endpoint,
properties, and dispatch list. Software projects are often tested
in a variety of environments or hardware configurations; as,
obviously, the performance might differ significantly (especially
depending on the used hardware) a proper analysis therefore requires
the possibility to distinguish the various backends. Adding the
effective configuration adds this posibility.
|
|
|
|
... in the summary, so that the user knows what to expect when
looking into the details-environment.
|
|
|
|
With the introduction of new exit codes, the presentation of
an invocation was changed to refrain from showing actions in
abnormal case failure already during analysis phase. However
ca8fd841736ca65fa4292887052c78243512962a did not include the case of
a successful build into the cases of normal circumstances. Fix this.
|
|
|
|
... if available. This can be useful, when presenting builds
that are mainly there to have artifacts available for manual
use.
|
|
When showing a tree, we have for each entry already a designated
file name. Use this, to offer direct dowload links for blobs with
the intended name.
|
|
With just-mr supporting a custom prefix to be shown at the beginning
of a logged invocation, users might be pointed to the web server very
early. Therefore, properly indicate if the invocation data is not yet
complete.
|
|
For many text files it is useful to read them directly in the browser.
However, many files that are better analysed by machines (like large
repository configurations) also come as plain-text files. Therefore,
always offer to download a file currently being viewed. Use the URL
scheme in such a way that the name to download the file as can be
specified; in this way, we are prepared if we decide to also log
the artifacts to be built and offer those to be downloaded.
|
|
|
|
Being able to browse through past invocations of the build tool can
actually be useful and doing so in the browser is a way many users
prefer. Therefore, add a small WSGI application (written in python,
using werkzeug and jinja) serving a directory of invocation logs
via http.
|
|
|
|
In preparation for the rule changes, to avoid introducing false
positives during future bisections.
|
|
|
|
... under the advanced chapter of our tutorial.
|
|
... and ensure that pandoc processes them correctly. In particular,
add an empty line around itemize environments.
|
|
|
|
|
|
|
|
- For the rule functions TREE_OVERLAY and DISJOINT_TREE_OVERLAY
call the argument "$1", to align with the argument name for
BLOB and TREE.
- For the built-in functions `"tree_overlay"` and `"disjoint_tree_overlay"`,
align this the built-in function `"tree"` and allow staging of
the resulting tree.
|
|
|
|
... and remove it from the future design, as it is already implemented.
|
