summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2025-02-07IExecutionApi: Rename IsAvailable to GetMissingDigestsMaksim Denisov
2025-02-07IExecutionApi: Use unordered_set in IsAvailableMaksim Denisov
2025-02-07Remove logging related to blob splitting form BazelApiMaksim Denisov
2025-02-07BazelCasClient: Use unordered_set in FindMissingBlobsMaksim Denisov
2025-02-07ContentBlob: Support hashingMaksim Denisov
2025-02-07DAG: Drop usage of TransformedRange.Maksim Denisov
2025-02-07Implement BackMapMaksim Denisov
...that is a container of Values mapped to Keys, and supports constant complexity search of a Value by a given Key
2025-02-06logging: switch time stamps to UTCKlaus Aehlig
Time stamps in local time without explicit time zone are ambigious, definitely at the end of daylight saving time. Moreover, even if explicit time zones were given, it is still unconvenient to correctly sort event expressed in different time zones. However, with increased use of `just serve`, logs originating from different machines become the norm. Therefore, normalize all time stamps to UTC (and explicitly state that this is the time zone used).
2025-02-05CHANGELOG: mention local-api fixKlaus Aehlig
2025-02-05Add basic end-to-end test for just-mr gc --drop-onlyKlaus Aehlig
2025-02-05just-mr(1): Document new option --drop-only for gc-repoKlaus Aehlig
2025-02-05just-mr gc-repo: support drop onlyKlaus Aehlig
As opposed to the regular CAS/cache, for the git repository implicit in the repository cache we cannot guarantee that data from older generation is always promoted via hard links. Therefore, a certain amount of data can be duplicated between the repo-cache generations. In order to allow compacting storage to the minimum, add an option to gc-repo to only remove the older generation, without rotating.
2025-02-05Repository garbage collector: support dropping onlyKlaus Aehlig
Add support for repository gargabe collection to only drop the older generations without rotating.
2025-02-05just-mr(1): document the gc-repo subcommandKlaus Aehlig
2025-01-30README: fix reference to tutorial sectionKlaus Aehlig
2025-01-30Add basic introduction on how to set up computed rootsKlaus Aehlig
2025-01-30CHANGELOG: document recent fix to `just-mr gc-repo`Klaus Aehlig
2025-01-30Add an end-to-end test for repeated repository garbage collectionKlaus Aehlig
As only a recent commit made it possible to rotate the repository cache more than once, add a test ensuring two properties. - Repeated repository gc is possible and roots are taken from the rotated generation. - It is possible to fully rotate a root out.
2025-01-29local api: absence of a git api is not a success in retrievingKlaus Aehlig
While there, also check for availability first, to avoid duplicated error messages (from git_cas and the caller).
2025-01-29just-lock: Search for archives to fetch also in Git cachePaul Cristian Sarbu
...before trying remotes.
2025-01-29just-lock: Run commit check command only on existing repositoriesPaul Cristian Sarbu
While there, improve docstrings of methods operating on Git repositories to specify when the underlying Git repositories are expected to be present.
2025-01-29just-lock: Add support for 'tree structure' rootsPaul Cristian Sarbu
Based on f0473730 and 22ef0a16
2025-01-29just-lock: Fix deduplication of 'computed' rootsPaul Cristian Sarbu
Based on 76ce2123
2025-01-29just-lock: Normalize subdir before checking if non-upwardPaul Cristian Sarbu
2025-01-29just-lock: Improve error handling for importing to GitPaul Cristian Sarbu
2025-01-29just-lock: Ensure all commands use the run_cmd methodPaul Cristian Sarbu
2025-01-29just-deduplicate-repos: Fix formattingPaul Cristian Sarbu
2025-01-29just-lock-config(5): Document the 'git tree' source typePaul Cristian Sarbu
2025-01-29just-lock config: Make field names consistent with just-mrPaul Cristian Sarbu
2025-01-29garbage collection: remove garbage recursivelyKlaus Aehlig
When garbage collecting the oldest generation, we expect it to be a non-empty directory. Therefore, remove it recursively.
2025-01-28Progress reporting: also report the primary action outputKlaus Aehlig
While reporting an origin target with action number within that target describes an action uniquely in a way meaningful to the user, it might not always be eay to unserstand which precise action is currently running. For example, for a library with many source files, we have a target generating a large number of actions and the association of source file to action number requires detailled knowledge of the build description. The name of the primary ouput of that action, on the other hand immediately identifies the file that is compiled. Therefore, report this as well.
2025-01-27Update libfmt to 11.1.3Klaus Aehlig
2025-01-24Add native comparison of configured targetsKlaus Aehlig
... and use it when normalizing the origins of actions. For this task, any well-defined linear order is sufficient. Using a native comparision (rather than comparing the canonical serialisation) significantly speeds up that normalisation process, as the assumption that it would be rare that an action has more than one origin turned out to be false. In fact, we have seeen cases where this sorting used to take several seconds before this change, so that this change reduced analysis time by more than a factor of 5.
2025-01-24Action equality test: only verify the set of originsKlaus Aehlig
While our tool promises to generate a reproducible order of the action origins, we should not insist on a particular one. Therefore sort before comparing.
2025-01-24Add test verifying the "generic" rule properly detecs staging conflictsKlaus Aehlig
2025-01-24"generic" rule: verify staging conflicts on inputsKlaus Aehlig
The "generic" rules deliberately resolves conflicts on identical paths in a latest-wins fashion (seeing all artifacts as later than all runfiles) to allow an easy way to define actions. However, the inputs stage obtained by this resolution can still contain conflicts and those are an error. Properly detect those. Also clarify in the documentation, that only conflicts on identical paths are resolved in the described priority, not semantic overlap.
2025-01-23Add basic end-to-end test on progress reportingKlaus Aehlig
2025-01-23Computed roots: add basic progress reportingKlaus Aehlig
2025-01-23Add basic progress reporter on root evaluationKlaus Aehlig
2025-01-23Remove unused library "root_utils"Maksim Denisov
2025-01-23JustMr: Replace calls to CheckServeHasAbsentRoot with direct calls to serveMaksim Denisov
2025-01-23PrecomputedRoot: Remove DownloadFromServeMaksim Denisov
... and replace it with a direct call to serve.
2025-01-23ServeApi: Implement DownloadTreeMaksim Denisov
2025-01-23PrecomputedRoots: Remove UploadToServeMaksim Denisov
... and replace it with a direct call to serve.
2025-01-23Remove function EnsureAbsentRootOnServeMaksim Denisov
...since it is superseded by ServeApi's method.
2025-01-23JustMr: ContentGitMap: Remove unused arguments.Maksim Denisov
2025-01-23JustMr: ContentGitMap: Use serve callsMaksim Denisov
...instead of EnsureAbsentRootOnServe.
2025-01-23JustMr: ContentGitMap: Remove code duplication.Maksim Denisov
2025-01-23JustMr: DistdirGitMap: Use serve callsMaksim Denisov
...instead of EnsureAbsentRootOnServe. And remove unused arguments.
2025-01-23JustMr: CommitGitMap: Remove unused arguments.Maksim Denisov
generated by cgit v1.2.3 (git 2.39.1) at 2025-07-14 16:29:38 +0000