When running the libwebrtc update scripts on the Mozilla git repo, we generated a set of patches were pushing to try fails. I've been able to distill the patches down to 2 patches where we're adding and then modifying a patch file under third_party/libwebrtc/moz-patch-stack. The patch files that directory are generated by using the `git format-patch` command. It seems to be related to non-ASCII characters in the patch file.
Bug 2006510 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When running the libwebrtc update scripts on the Mozilla git repo, we generated a set of patches were pushing to try fails. I've been able to distill the patches down to 2 patches where we're adding and then modifying a patch file under third_party/libwebrtc/moz-patch-stack. The patch files that directory are generated by using the `git format-patch` command. It seems to be related to non-ASCII characters in the patch file. For historical purposes, the try command I'm using to test this is ```./mach try fuzzy --full -q '^source-test-mozlint-py-ruff'```, but the issue happens with other query strings. The email I get from Lando states: Your request to land try push with tip commit 'WIP: Vendor libwebrtc from 6cccb107b8' failed. Reason: Problem while applying patch in revision None: hg error in cmd: hg import --no-commit -s 95 /tmp/tmpkiz3eoxx: applying /tmp/tmpkiz3eoxx patching file third_party/libwebrtc/moz-patch-stack/p0003.patch Hunk #1 FAILED at 0 1 out of 1 hunks FAILED -- saving rejects to file third_party/libwebrtc/moz-patch-stack/p0003.patch.rej abort: patch failed to apply
When running the libwebrtc update scripts on the Mozilla git repo, we generated a set of patches were pushing to try fails. I've been able to distill the patches down to 2 patches where we're adding and then modifying a patch file under third_party/libwebrtc/moz-patch-stack. The patch files that directory are generated by using the `git format-patch` command. It seems to be related to non-ASCII characters in the patch file. For historical purposes, the try command I'm using to test this is `./mach try fuzzy --full -q '^source-test-mozlint-py-ruff'`, but the issue happens with other query strings. The email I get from Lando states: ``` Your request to land try push with tip commit 'WIP: Vendor libwebrtc from 6cccb107b8' failed. Reason: Problem while applying patch in revision None: hg error in cmd: hg import --no-commit -s 95 /tmp/tmpkiz3eoxx: applying /tmp/tmpkiz3eoxx patching file third_party/libwebrtc/moz-patch-stack/p0003.patch Hunk #1 FAILED at 0 1 out of 1 hunks FAILED -- saving rejects to file third_party/libwebrtc/moz-patch-stack/p0003.patch.rej abort: patch failed to apply ```