Skip to content

MAISTRA-2648: WASM fix for s390x#134

Merged
maistra-bot merged 1 commit intomaistra:maistra-2.1from
knm3000:wasm-on-z
Mar 17, 2022
Merged

MAISTRA-2648: WASM fix for s390x#134
maistra-bot merged 1 commit intomaistra:maistra-2.1from
knm3000:wasm-on-z

Conversation

@knm3000
Copy link
Contributor

@knm3000 knm3000 commented Feb 21, 2022

Fixes https://issues.redhat.com/browse/MAISTRA-2648
The permanent fix is not a part of maistra/envoy yet:
proxy-wasm/proxy-wasm-cpp-host#198

Signed-off-by: Konstantin Maksimov konstantin.maksimov@ibm.com

@maistra-bot
Copy link

Hi @knm3000. Thanks for your PR.

I'm waiting for a maistra member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jwendell
Copy link
Member

/ok-to-test

Copy link
Contributor

@oschaaf oschaaf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @knm3000 for moving the change into this repo.
I have no other comments, LGTM

@oschaaf
Copy link
Contributor

oschaaf commented Feb 21, 2022

Note: I tagged this PR with do-not merge as I think @twghu should be able to gate this (I also added him as a reviewer) - he may have a large set of changes inbound for the target branch, and it might help if the target doesn't move.

@oschaaf
Copy link
Contributor

oschaaf commented Feb 21, 2022

Sorry - I misread the target branch; please disregard the earlier comment. I removed the do-not-merge label. Sorry about the noise!

@jwendell
Copy link
Member

/retest

build_file = "@envoy//bazel/external:proxy_wasm_cpp_host.BUILD",
# The patch fixes WASM on s390x https://issues.redhat.com/browse/MAISTRA-2648
# The permanent fix is https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/198
patches = ["@envoy//bazel/external:proxy_wasm_cpp_host.patch"],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Generally speaking it's a good idea to name the file after its meaning or purpose, or even with the title of the original patch, instead of naming it with the name of the package. What if, in the future there is another patch for this same package?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed the patch file name to proxy_wasm_s390x.patch.

Fixes https://issues.redhat.com/browse/MAISTRA-2648
The permanent fix is not a part of maistra/envoy yet:
proxy-wasm/proxy-wasm-cpp-host#198

Signed-off-by: Konstantin Maksimov <konstantin.maksimov@ibm.com>
@jwendell
Copy link
Member

/retest

@oschaaf
Copy link
Contributor

oschaaf commented Mar 14, 2022

/retest

@maistra-bot maistra-bot merged commit 75168a1 into maistra:maistra-2.1 Mar 17, 2022
rcernich added a commit that referenced this pull request Mar 25, 2022
maistra-bot pushed a commit that referenced this pull request Mar 25, 2022
@knm3000 knm3000 deleted the wasm-on-z branch June 2, 2022 12:31
dcillera pushed a commit to dcillera/envoy that referenced this pull request Feb 19, 2024
Fixes https://issues.redhat.com/browse/MAISTRA-2648
The permanent fix is not a part of maistra/envoy yet:
proxy-wasm/proxy-wasm-cpp-host#198

Signed-off-by: Konstantin Maksimov <konstantin.maksimov@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants