Double timeouts for Socket Broker tests.

There are flakes in the Socket Broker tests see

https://analysis.chromium.org/p/chromium/flake-portal/flakes?flake_filter=binary%3A%3Asbox_integration_tests

This CL extends the timeout so they flakes should go away.

BUG=None

Change-Id: I5672d53e2ae3acf5cdf3eb57104f98dfa1248c9c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3083322
Reviewed-by: Alex Gough <ajgo@chromium.org>
Commit-Queue: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#910052}
NOKEYCHECK=True
GitOrigin-RevId: 00c08c16ce8821524e2ecb24392f57fdd06616d2
1 file changed
tree: 608d6a152f37a81ce017a101003760e7079aae49
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  6. constants.h
  7. DEPS
  8. DIR_METADATA
  9. features.gni
  10. ipc.dict
  11. OWNERS
  12. README.md
  13. sandbox_export.h
README.md

Sandbox Library

This directory contains platform-specific sandboxing libraries. Sandboxing is a technique that can improve the security of an application by separating untrustworthy code (or code that handles untrustworthy data) and restricting its privileges and capabilities.

Each platform relies on the operating system's process primitive to isolate code into distinct security principals, and platform-specific technologies are used to implement the privilege reduction. At a high-level:

  • mac/ uses the Seatbelt sandbox. See the detailed design for more.
  • linux/ uses namespaces and Seccomp-BPF. See the detailed design for more.
  • win/ uses a combination of restricted tokens, distinct job objects, alternate desktops, and integrity levels. See the detailed design for more.

Built on top of the low-level sandboxing library is the //sandbox/policy component, which provides concrete policies and helper utilities for sandboxing specific Chromium processes and services. The core sandbox library cannot depend on the policy component.