Add instructions for local testing with s390x by leonm1 · Pull Request #530 · proxy-wasm/proxy-wasm-cpp-host

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 · 2026-03-18T18:42:08Z

No description provided.

Signed-off-by: Matt Leon <mattleon@google.com>

PiotrSikora · 2026-03-19T02:23:00Z

+docker run --env HOME=$HOME --env USER=$(id -un) --volume "$HOME:$HOME" --workdir $(pwd) --user $(id -u):$(id -g) --platform linux/s390x --interactive -t --env PS1="docker (s390x):" ghcr.io/proxy-wasm/build-tools:ubuntu-24.04-bazel-7.7.1 bash
+
+# Set a useful prompt to remind yourself this shell is in s390x:
+export PS1='docker@s390x:\[\033[01;34m\]\w\[\033[00m\] )> '


You're already configuring PS1 in the docker invocation.

PiotrSikora · 2026-03-19T16:07:18Z

+```bash
+bazel build --verbose_failures --test_output=errors --config=clang --config=hermetic-llvm -c opt $(bazel query 'kind(was.*_rust_binary, //test/test_data/...)') $(bazel query 'kind(_optimized_wasm_cc_binary, //test/test_data/...)')
+
+# Copy the built artifacts to the test_data dir.
+cp bazel-bin/test/test_data/*.wasm test/test_data/
+
+# Rewrite test/test_data/BUILD to use the pre-built wasm module artifacts
+echo "package(default_visibility = [\"//visibility:public\"])" > test/test_data/BUILD
+for i in $(cd test/test_data && ls -1 *.wasm | sed 's/\.wasm$//g'); do \
+ echo "filegroup(name = \"$i\", srcs = [\"$i.wasm\"])" >> test/test_data/BUILD; \
+done
+# Rewrite test/BUILD to use the pre-built artifacts
+sed 's/\.wasm//g' test/BUILD > test/BUILD.tmp && mv test/BUILD.tmp test/BUILD
+```


Since this is a bit error prone and repeated here and in the CI, perhaps extract this to a script?
Alternatively, maybe we should fix building test data on S390x? Rust modules should just work, since we're building Wasmtime, and we could either check if Emscripten supports S390x or perhaps skip tests using C++ SDK when testing locally?

PiotrSikora · 2026-03-19T16:07:49Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).


Maybe just include those 2 lines here instead of linking?

PiotrSikora · 2026-03-19T16:08:04Z

+s390x tests can be run locally using the build-tools docker images published in
+this repo. An s390x QEMU emulator is required to be installed ([example
+instructions](https://docs.gitlab.com/omnibus/development/s390x/#vm-provisioning)).
+The following command will start an interactive session in an emulated s390x


Nit: missing separation between paragraphs.

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

leonm1 requested review from PiotrSikora, martijneken and mpwarres as code owners March 18, 2026 18:42

Add instructions for local testing with s390x
74e7f1e
Signed-off-by: Matt Leon <mattleon@google.com>

leonm1 force-pushed the docs/s390x branch from b3df4af to 74e7f1eCompare March 18, 2026 21:31

PiotrSikora reviewed Mar 19, 2026
View reviewed changes

Uh oh!

Conversation

leonm1 commented Mar 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

leonm1 commented Mar 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

leonm1 commented Mar 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

leonm1 commented Mar 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants