Age | Commit message (Collapse) | Author | |
---|---|---|---|
5 days | doc: Fix various typos and inconsistencies | Paul Cristian Sarbu | |
5 days | Documentation: fix typos | Klaus Aehlig | |
7 days | future-designs: Remove entries for debug fission and just-lock | Paul Cristian Sarbu | |
...as these features have already been implemented and appropriately documented. | |||
9 days | Tutorial: also point to the computed root used in the justbuild repo | Klaus Aehlig | |
9 days | Documentation: fix default for "main" in repository-config | Klaus Aehlig | |
9 days | Documentation: fix some typos | Klaus Aehlig | |
14 days | Invocation server: directly show only artifact | Klaus Aehlig | |
When presenting a build, the output artifacts are hidden behind a "details" environment to not overload the user with long list of, e.g., test results (especially if generated by a test matrix). If, however, only a single artifact is built, there is no reason to hide it; so simply show it. | |||
2025-06-13 | Extend invocation-logging tutorial | Klaus Aehlig | |
Environment variables can be used to provide some context, why a particular invocation was run, and hence allow additional sharding. Also, remind that setting up a cronjob for log rotation might me a good idea. | |||
2025-06-12 | Update documentation | Maksim Denisov | |
2025-06-11 | Add design document for full GC | Maksim Denisov | |
2025-06-05 | lint tutorial: hint on the discovered but not processed actions | Klaus Aehlig | |
Linting is a natural example where actions are discovered that are not neded for the artifact that is requested to be built. Use this opportunity to explain the difference between discovering an action and processing it. | |||
2025-06-05 | tutorial lint: Update example output | Paul Cristian Sarbu | |
2025-06-03 | Invocation server: also show counts in headings | Klaus Aehlig | |
Often, the simple number, e.g., for failed actions can already give valuable information. For example, when investigating flakiness, the count of failed actions already gives a hint whether a change increased or decreased flakiness which can be valuable before even investigating if the nature of the failure has changed. As we have that information available and an additional number in a heading does not clutter the page too much, let's just show it. | |||
2025-05-30 | Invocation server: add links back to the overview page | Klaus Aehlig | |
2025-05-30 | Invocation server: use "build stop time" for build wall-clock time | Klaus Aehlig | |
As the end of the build can be significantly ahead of the end of the incvocation, a new time stamp was added to the profile. Use this new time stamp in the invocation server when determining the wall-clock time of the build. | |||
2025-05-28 | Invocation server: also show the build time | Klaus Aehlig | |
Also show only the build time in the invocations overview, as only for the build phase detailled timing information will be available in the log of a particular information. | |||
2025-05-23 | tutorial: Update example outputs in all chapters | Paul Cristian Sarbu | |
...to match the ones produces by latest binaries and rules. | |||
2025-05-23 | tutorial computed: Fix source of non-reproducibility in example script | Paul Cristian Sarbu | |
While there, update outputs to what is expected with current released binaries and rules. Co-authored-by: Klaus Aehlig <klaus.aehlig@huawei.com> | |||
2025-05-23 | tutorial: Add DWP and ADD_DEBUGFLAGS | Paul Cristian Sarbu | |
...to example export targets and defaults. | |||
2025-05-23 | tutorial debugging: Use ADD_COMPILE_FLAGS | Paul Cristian Sarbu | |
...instead of replacing CFLAGS and CXXFLAGS, thus also fixing a mismatch introduced in c008c07656fff528c80add260397c7c7702aa2a8. | |||
2025-05-23 | Extend tutorial on cross compiling showing how to use ["test", "matrix"] | Klaus Aehlig | |
2025-05-22 | invocation server: add presentation of invocation wall-clock time | Sascha Roloff | |
2025-05-21 | invocation server: fix download links | Klaus Aehlig | |
... to include only the basename of the requested artifact. | |||
2025-05-20 | invocation server: add critical-path computation | Sascha Roloff | |
2025-05-20 | invocation server: move show_action macro into separate template file | Sascha Roloff | |
... to allow reuse. | |||
2025-05-20 | invocation server: move action_data function out of do_get_invocation method | Sascha Roloff | |
... to allow reuse. | |||
2025-05-20 | invocation server: fix typo | Sascha Roloff | |
2025-05-15 | just-mr: support invocation-specific artifacts-to-build logging | Klaus Aehlig | |
It is already supported to ask just-mr (via the rc file) to log for each invocation the artifacts that were built. Add a similar option for the artifacts that were to be built, i.e., for dumping the intensional description of the output artifacts. That information can be used, e.g., to compute the critical path. | |||
2025-05-15 | invocation server: fix isintance statement | Klaus Aehlig | |
2025-05-15 | Invocation server: add target filter | Sascha Roloff | |
2025-05-15 | Invocation server: add remote-execution address filter | Sascha Roloff | |
2025-05-15 | Invocation server: lexicographically sort filter keys | Sascha Roloff | |
2025-05-15 | Invocation server: print nothing for empty remote-execution properties | Sascha Roloff | |
2025-05-15 | Invocation server: print only non-empty dispatch lists | Sascha Roloff | |
2025-05-15 | Invocation server: add missing HTML-escape filters in templates | Sascha Roloff | |
2025-05-15 | Invocation server: uncollapse first failed action | Sascha Roloff | |
2025-05-15 | tutorial invocation logging: include --dump-artifacts | Klaus Aehlig | |
A typical invocation logging would also include a value for "--dump-artifacts". Mention this in the tutorial. | |||
2025-05-14 | tutorial, test: recommend ["test", "suite"] for combining tests | Klaus Aehlig | |
... as this also works together with, e.g., linting. While there, also rerun the examples to get the latest output messages. | |||
2025-05-14 | Invocation server: make command-line collapsible | Sascha Roloff | |
2025-05-13 | Invocation server: load more invocations with reduced information | Sascha Roloff | |
2025-05-13 | Invocation server: adapt style | Sascha Roloff | |
2025-05-13 | Invocation server: lexicographically sort filter values | Sascha Roloff | |
2025-05-13 | Invocation server: include commandline when describing actions | Klaus Aehlig | |
2025-05-13 | Invocation server: show actions with console output separately | Klaus Aehlig | |
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). | |||
2025-05-13 | Invocation server: add links to blob references in analysis errors | Klaus Aehlig | |
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. | |||
2025-05-13 | Invocation server: fix hash pattern | Klaus Aehlig | |
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. | |||
2025-05-13 | Tutorial: Update reference to rules-cc | Oliver Reiche | |
2025-05-12 | Invocation server: add css style file | Sascha Roloff | |
2025-05-12 | Invocation server: add filter selector to overview page | Sascha Roloff | |
2025-05-12 | Invocation server: support restricting to not-fully-cached builds | Klaus Aehlig | |