Add a prompt eval for getting the build target This is a modified version of a test from the doc. There is a concern that adding this test will cause the model to get trained on it and defeat the purpose of the test so I've changed the file and target. It might be interesting to see if this specific target/file becomes more reliable than other files/targets. I can also abandon this if there's any concern about adding a test too similar to the ones being collected Bug: 443097039 Change-Id: I774d2b41664204565c19c1867f52f4deb2f68f31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6918154 Reviewed-by: Dominic Battré <battre@chromium.org> Reviewed-by: Erik Staab <estaab@chromium.org> Commit-Queue: Struan Shrimpton <sshrimp@google.com> Cr-Commit-Position: refs/heads/main@{#1515755}
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.
If you found a bug, please file it at https://crbug.com/new.