You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In OpenTitan, we use bazel to coordinate and direct tests, and we have long running tests on simulators and on FPGAs. The FPGA tests require exclusive access to attached FPGAs, but don't conflict with any of the non-FPGA actions in our WORKSPACE. #16785 and it's predecessors offer a means to introduce extra resources like our fpga boards and issue tests in parallel with other actions, but without issuing multiple tests that require the FPGAs.
I can't find an open issue referenced in this work so I'm writing it up
What underlying problem are you trying to solve with this feature?
We're trying to make our WORKSPACE aware of resource limitations that aren't covered by the CPU/Memory limits and aren't covered by "exclusive" tags or controlling the number of jobs without incurring a large overhead.
Which operating system are you running Bazel on?
Rolling debian testing Rodette
What is the output of bazel info release?
release 5.3.2
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?
This recreates a [closed PR](#13996) to implement extra resources which we're hoping to use in lowRISC/opentitan#16436
Fixes:#16817Closes#16785.
PiperOrigin-RevId: 498557024
Change-Id: I60d8f8f4a4a02748147cabb4cd60a2a9b95a2c68
This recreates a [closed PR](#13996) to implement extra resources which we're hoping to use in lowRISC/opentitan#16436
Fixes:#16817Closes#16785.
PiperOrigin-RevId: 498557024
Change-Id: I60d8f8f4a4a02748147cabb4cd60a2a9b95a2c68
Co-authored-by: kshyanashree <109167932+kshyanashree@users.noreply.github.com>
This recreates a [closed PR](#13996) to implement extra resources which we're hoping to use in lowRISC/opentitan#16436
Fixes:#16817Closes#16785.
PiperOrigin-RevId: 498557024
Change-Id: I60d8f8f4a4a02748147cabb4cd60a2a9b95a2c68
Description of the feature request:
In OpenTitan, we use bazel to coordinate and direct tests, and we have long running tests on simulators and on FPGAs. The FPGA tests require exclusive access to attached FPGAs, but don't conflict with any of the non-FPGA actions in our WORKSPACE.
#16785 and it's predecessors offer a means to introduce extra resources like our fpga boards and issue tests in parallel with other actions, but without issuing multiple tests that require the FPGAs.
I can't find an open issue referenced in this work so I'm writing it up
What underlying problem are you trying to solve with this feature?
We're trying to make our WORKSPACE aware of resource limitations that aren't covered by the CPU/Memory limits and aren't covered by "exclusive" tags or controlling the number of jobs without incurring a large overhead.
Which operating system are you running Bazel on?
Rolling debian testing Rodette
What is the output of
bazel info release
?release 5.3.2
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?Have you found anything relevant by searching the web?
More discussion here: #16785
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: