Fix field_trial deserialization unittest
Use a plausible file descriptor number instead of -1 for constructing
a shared memory handle in the serialization test.
The value doesn't really matter for the test since it doesn't actually
use the file descriptor, but using -1 broke a sanity check I'm adding
in a new CL that adds a new Android shared memory handle subtype. See
https: //crrev.com/c/680100 for context.
Bug:
Change-Id: If16a7491e2f446d1a28af171fc4536aec540d755
Reviewed-on: https://chromium-review.googlesource.com/735534
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#511739}
CrOS-Libchrome-Original-Commit: ec082c81353aa08ef66263e31a477b3c973d1ab8
1 file changed