Revert "Mojo: NodeChannel should require a minimum size when using multiple versions"
This reverts commit 8ad25003. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 828478 as the culprit for flakes in the build cycles as shown on: https://analysis.chromium.org/p/chromium/flake-portal/analysis/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vOGFkMjUwMDNkZTgwODIxMjhjM2IzNDU2NWVhMjg4ZGM3OGZhODhkYgw Sample Failed Build: https://ci.chromium.org/b/8863329295603494640 Sample Failed Step: mojo_unittests on (none) GPU on Mac on Mac-10.14.6 Sample Flaky Test: NodeChannelTest.MessagesCannotBeSmallerThanOldestVersion Original change's description: > Mojo: NodeChannel should require a minimum size when using multiple versions > > When we added support for versioned message we accidentally introduced a > behavior where messages can be shorter than expected. This is what the > behavior should be to allow older messages to be received. However, > we know the minimum size is the oldest message version. We should > never be allowed to go smaller than that. > > BUG=chromium:1149805 > > Change-Id: I3a24dd62b6fafd742cd7ac155f863d33bb5c6de8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2545207 > Reviewed-by: Ken Rockot <rockot@google.com> > Commit-Queue: Brian Geffon <bgeffon@chromium.org> > Cr-Commit-Position: refs/heads/master@{#828478} No-Presubmit: true No-Tree-Checks: true No-Try: true BUG=chromium:1149805 Change-Id: I0bb4a4605a1f705c4388769fae4559e0835d1980 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2546460 Cr-Commit-Position: refs/heads/master@{#828581}
Showing
Please register or sign in to comment