Geoffrey Martin-Noble

Handle GPU resource management in ctest

9

Currently the integration tests running on real GPUs are frequently failing due to running out of GPU memory (https://source.cloud.google.com/results/invocations/5a6a9122-9c10-4a92-a4c5-d8fad601b58a/targets/iree%2Fgcp_ubuntu%2Fcmake-bazel%2Flinux%2Fx86-turing%2Fmain/log): > RuntimeError: Error invoking function: /tmpfs/src/github/iree/iree/hal/vulkan/status_util.c:53: RESOURCE_EXHAUSTED; VK_ERROR_OUT_OF_DEVICE_MEMORY; vmaCreateBuffer; while invoking...

Make self-hosted GitHub runners ephemeral (and gracefully deregister)

4

Our self-hosted GitHub runners autoscale in a Managed Instance Group, but are currently not ephemeral. This means that state from one build can influence a subsequent build. We take some...

**Describe the bug** If you check "Override location-based data" you are now required to input all fields in order to be able to set the activity parameters, even if not...

Ability to configure which warnings to use

5

It would be great if the extension allowed configuration for which buildifier warnings to use (matching the `--warnings` flag to buildifier).

For collection-type properties. This would be really nice. Thanks for the cool plugin :-) https://github.com/google/auto/blob/master/value/userguide/builders-howto.md#add

Buildifier warns about lack of rules_cc; rules_cc says you don't have to use it

1

> native-cc: Function "cc_library" is not global anymore and needs to be loaded from "@rules_cc//cc:defs.bzl". (https://github.com/bazelbuild/buildtools/blob/master/WARNINGS.md#native-cc) > There is no need to use rules from this repository just yet. If...

rng_uniform lowering to vmvx has undefined behavior

6

When running `tests/e2e/xla_ops:check_vmvx_local-task_rng_uniform.mlir` with ubsan internally, I'm hitting: `UndefinedBehaviorSanitizer: signed-integer-overflow runtime/src/iree/vm/ops.h:47` @kuhar, who I believe is looking into ubsan errors. That's the VM mul: `static inline int32_t vm_mul_i32(int32_t lhs, int32_t...

skip-ci

TSan failure in `TaskWaitTest.IssueTimeout`

5

I'm seeing what I think is a flaky TSan failure in `TaskWaitTest.IssueTimeout`. This is in testing a new runner configuration, so I suppose it's *possible* that this is somehow caused...