From 9ff01a766d98359c7dcf199aa6c4fba7fb427140 Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Wed, 7 May 2025 10:22:39 +0200 Subject: profile: include remote-execution properties 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. --- doc/concepts/profiling.md | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'doc') diff --git a/doc/concepts/profiling.md b/doc/concepts/profiling.md index f63bc91f..4030b638 100644 --- a/doc/concepts/profiling.md +++ b/doc/concepts/profiling.md @@ -109,6 +109,13 @@ more keys possibly added in the future). is a value derived not only from the command line but also from the context of a file (given via `-c`) possibly local on the machine `just` was run. + - The key `"remote"` describes the remote-exeuction endpoint, + including the used properties and dispatch list. This allow + distinguishing builds in different environments (possibly using + different hardware); this can be relevant both for performance + as well as failure statistics for tests. Again, the reason for + including it in the profile is that local files are read (for + the dispatch list). - The key `"actions"` contains a JSON object with the keys being precisely the key identifiers of the actions attempted to run. The action identifiers are the same as in the `--dump-graph` or -- cgit v1.2.3