Google Git
Sign in
chromium / chromiumos / platform / cbor / refs/heads/stabilize-15174.B
commit55b123398489027c07a31f4e0fdb3613aef8695d[log] [tgz]
authorNavil Perez <[email protected]>Mon Sep 26 23:28:08 2022
committerChromeos LUCI <[email protected]>Tue Sep 27 22:17:33 2022
treee8fd8a95e6a712043e81e7854efcb34b0f9472d1
parent35fe21779fddc0d376da13dab49e31fa3491205f [diff]
DIR_METADATA: Add V2 Test Plans.

Add the default set of test rules.

V2 test plans will be verified in staging before being enabled in prod.

See go/cros-cq-test-config for more details.

BUG=b:249150178
TEST=dirmd validate

Change-Id: I83c3313767374a51832361c434e48d0daf677507
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/cbor/+/3920418
Reviewed-by: Tom Hughes <[email protected]>
Commit-Queue: Navil Perez <[email protected]>
Reviewed-by: Andrew Lamb <[email protected]>
Tested-by: Navil Perez <[email protected]>
1 file changed
tree: e8fd8a95e6a712043e81e7854efcb34b0f9472d1
  1. reader_fuzzer_corpus/
  2. BUILD.gn
  3. cbor_export.h
  4. constants.h
  5. diagnostic_writer.cc
  6. diagnostic_writer.h
  7. diagnostic_writer_unittest.cc
  8. DIR_METADATA
  9. OWNERS
  10. reader.cc
  11. reader.h
  12. reader_fuzzer.cc
  13. reader_unittest.cc
  14. README.md
  15. values.cc
  16. values.h
  17. values_unittest.cc
  18. writer.cc
  19. writer.h
  20. writer_unittest.cc
README.md

cbor: Concise Binary Object Representation

This library is a partial implementation of the RFC 7049 Concise Binary Object Representation standard.

The source code was fetched from chromium/src in order to avoid code duplication.

The cros/upstream/main branch is a mirror of the components/cbor directory from upstream. It is automatically updated to reflect the latest changes in upstream.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update

  • git checkout -b main cros/main

  • git merge cros/upstream/main

    • Expect merge conflicts, because of the difference in header paths.
    • OWNERS should use the version from main.
    • BUILD.gn should mostly use the version from main, unless the upstream changes the files to be built.
    • The #include paths should use the version from main (without “components/”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to do make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use git revert after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.

  • Push the resulting merge commit with:

    (chroot) $ git push HEAD:refs/for/main