[roll] Roll fuchsia [netstack3] Fix a logic error when handling SYN for TIME_WAIT A logic error of using `last_seq` instead of `last_ack` when checking if the sequence number is acceptable has caused flakes in CI. This was not caught by any unit test because the unit tests are deterministic and they always use the same local port so that the same sequence number being generated every time a new connection is created. However, a new unit test is not added because it would assume the underlying hash algo, which makes the test a change detector. Multiply: netstack3_loopback_isolated_syscall_tests Original-Fixed: 127205 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/858671 Original-Revision: 7ba1e56b8f29139ad913129daf87ad740c253f50 GitOrigin-RevId: 1cc47e45180c5aa62211e47d39c2193924a71270 Change-Id: Ie6f1ded719ca2557bb6c659d1bc7c3fc26b85a6c
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.