Scott Todd
Scott Todd
As part of moving more jobs from ci.yml go pkgci.yml, I've been chipping away at our use of Docker images. Better to not use Docker at all if we can...
Seems like we could fork https://github.com/nod-ai/base-docker-images into iree-org and iterate from there. Can keep the original repo in nod-ai so existing packages continue to exist and new dockerfiles/images specific to...
> Seems like we could fork https://github.com/nod-ai/base-docker-images into iree-org and iterate from there. Can keep the original repo in nod-ai so existing packages continue to exist and new dockerfiles/images specific...
Oooh, the test crash is flaky. That makes bisecting trickier... would be easier on Linux with ASan. I tried around 10 times at `iree_compiler==20240418.867` and can't repro there.
I've almost finished switching workflows to using dockerfiles hosted at https://github.com/iree-org/base-docker-images/. Here's what's left: - [x] `build_test_all_bazel` in `ci.yml` uses `gcr.io/iree-oss/base-bleeding-edge` - [x] `build:remote_cache_bazel_ci` in `iree.bazelrc` uses `gcr.io/iree-oss/base-bleeding-edge` in the...
Still verifying with ASan on Linux to avoid the flakes, but my bisect on Windows seems to be pointing to https://github.com/iree-org/iree/commit/f32a87ccd2 for the test crash. That's "mostly" an NFC according...
For Bazel, we could try using https://bazel.build/install/docker-container (e.g. `gcr.io/bazel-public/bazel:latest`). That wouldn't have any of our other build deps or configurations for ramdisks, remote caches, etc. baked in though... if any...
Bah, having trouble pinning this down. * Linux segfaults in my Python unit test on package versions as old as `20240410.859` (and possibly earlier). * Linux source builds with ASan...
Actually nevermind RE: Bazel...? The source for that is https://github.com/bazelbuild/continuous-integration/blob/master/bazel/oci/Dockerfile and it's just for _using Bazel_. The entrypoint is hardcoded to `/usr/local/bin/bazel`, when I think we really just want a...
:/ yeah, .vmfb files produced before and after https://github.com/iree-org/iree/commit/f32a87ccd2 are identical and that commit didn't modify runtime code or python bindings. That's what my bisect pointed to though. Going to...