rrbutani

known:

• ctx.expand_location expands to .path, not short_path
  • there's a hidden kwarg (that we are not allowed to use) short_paths that provides the latter...

to be determined (by this experiment):

1. are variables provided via the toolchains attr implicitly added to ctx.var?
2. how do rules, in practice, grab files from elements in toolchains and add them to the inputs of the action(s) crafted?
3. what targets/files are implicitly available to ctx.expand_location?

rrbutani

slang solution1.sv --enable-legacy-protect -I . -Wno-protected-envelope
slang solution2.sv --enable-legacy-protect -I . -Wno-protected-envelope --translate-off-format slang_pragma,translate_off,translate_on

rrbutani

VCS UUM Library Experiments

....

Notes on Library Ordering

notes:

• post-order (children before parents) order is what makes sense for

rrbutani

default on attr.label (and attr.label_list, attr.string_keyed_label_dict) can be a function!

• but: only for private attributes

this includes things like "late bound defaults"

but also your own functions can ask for other (public) attributes of the rule as keyword args and use them to compute a default!

a neat alternative to initializers on rules

rrbutani

Previously we explored a way to have some degree of dynamic dependencies in Bazel (input "subsetting") using TreeArtifacts.

The particular use case modeled in the previous gist involved:

• a language with somewhat coarse library and binary rules (i.e. each rule describes a collection of files and their collective dependencies — the default for most Bazel rulesets)
• a monolithic (and slow!) compiler whose compilation unit size is the entire binary (rather than something smaller like modules or source files)
  • i.e. exacerbating the pain of not having "perfect" file-level dependency information
• source files that can be easily (and quickly) scanned to determine which dependencies are unused

rrbutani

...

rrbutani

❯ pytest --chrome-trace parallel-baseline.json -n auto --dist=worksteal
664 passed, 24 warnings in 9.08s

❯ pytest --chrome-trace parallel-reordered.json -n auto --dist=worksteal --expensive-tests-first

rrbutani

We couldn’t find that file to show.

rrbutani

observations:

1. path mapping does not really[^1] "mask" out the repo name from non-main repo paths: source files OR generated artifacts
   • this means that whether you build a particular target (or really produce a particular action for the target) when that target is in the main (root) repo vs. when its in an "external" repo effects the paths used in the action
   • i.e. you will not get cache hits if you build //:your_target and then pull your repo into another bazel workspace as @foo and build @foo//:your_target
   • TODO: would be nice to repo names as well...
2. path mapping silently falls back to using unmapped paths if the set of mapped paths has any conflicts (see :example_both)

• note that ctx.actions.run(_shell)'s inputs does influence path mapping and does appear to factor into how conflicts are detected but... if you try to add a path to the command line (i.e. via arguments) that you haven't listed in inputs it isn't an error — some path mapping heuristi

rrbutani

Enforcement of allowed dep edges

the idea is to have testonly-esque checks

consider a project where we want to partition content (for an existing rule) into three categories:

• "open-source"; a.k.a. oss
• "proprietary"; a.k.a. prp
• "development-only"; a.k.a. dev