commit | 70168522a8a50003ce56471958983f1415fcc020 | [log] [tgz] |
---|---|---|
author | Wojciech Replin <wreplin@opera.com> | Fri Feb 26 15:38:47 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 26 15:38:47 2021 |
tree | 0ce8ad63e57d3746c37a21d1664bb1a4103454b9 | |
parent | 2712443b433885c11b583a39e4936027fb76f292 [diff] |
Make cookie monster tests independent of system clock resolution Pass cookie creation time in PopulateCmForPredicateCheck Pass desired cookie creation time in cookie monster test R=chlily@chromium.org, morlovich@chromium.org Change-Id: Iaf088b313d1f7962f797f9a965632a7c74b52ca2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2698430 Reviewed-by: Lily Chen <chlily@chromium.org> Commit-Queue: Lily Chen <chlily@chromium.org> Cr-Commit-Position: refs/heads/master@{#858125}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.