This does no remove the existing configs, since there is a chrome
infrastructure change that needs to occur to point LUCI at the new
configs.
BUG=tint:693
Change-Id: Ie32427c51dde3386d6ca15e5dfc0222afe5c1f92
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/51401
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
BUG=chromium:1212166
Change-Id: I605fd926e0235da4f8e5b60bd471971dc1bded32
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/52021
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
These configs match the output of the new Starlark generated configs
that are being worked on. Landing these in advance to a) confirm that
they working, and b) make the patch using Starlark a no-op from the
config contents perspective.
Contains f3dcbf5c5c and
dffb68e49d that were reverted.
BUG=tint:693
Change-Id: Idf03edac2d318695a8088b9f779803b431da9e8c
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/51820
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Tripping a check related to not using goma on these builds.
BUG=tint:693
Change-Id: Ibcb20a5707abe887628ef41f12383bb0fae396e9
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/51600
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Ben Clayton <bclayton@google.com>
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
Commit-Queue: Ben Clayton <bclayton@google.com>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
BUG=tint:693
Change-Id: I451b98883972b96b8320dbfeeabd66c947aba8bc
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/51580
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Jamie Madill <jmadill@google.com>
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
These configs match the output of the new Starlark generated configs
that are being worked on. Landing these in advance to a) confirm that
they working, and b) make the patch using Starlark a no-op from the
config contents perspective.
BUG=tint:693
Change-Id: I82a85405097ae2e595c87f658027eddaa75e21a9
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/51400
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Jamie Madill <jmadill@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Tricium today is not working for tint because it has not been migrated
to recipe-based. The removal also unblocks the lucicfg migration for
tint.
R=rharrison
Bug: chromium:1155210, tint:693
Change-Id: I5d85801ffaddde0c9cbd5f04af8ca580684a504d
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/47903
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Win7 is not supported by Chromium builds anymore, so upstream has
introduced breaking changes.
BUG=tint:465
Change-Id: I6856f706bacf353808a2f7c536fbf8bb84ae9acd
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/39064
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Commit-Queue: dan sinclair <dsinclair@chromium.org>
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
Reviewed-by: dan sinclair <dsinclair@chromium.org>
This CL adds a tricium config file for Tint.
Change-Id: I08409df9b6b79bdd3ffecf4f28867674435ae14a
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/34360
Auto-Submit: dan sinclair <dsinclair@chromium.org>
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
After submitting the last CL I received an email with the note:
Some configs in revision 780c594 in tint repo have validation errors.
luci-config had to reject all configs in this revision.
* ERROR: refs.cfg: refs.cfg is not used since 2019 and must be deleted
Change-Id: I40c4fcdccd9af53aa47e32f074065782876f179d
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/25080
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
The try job group is project-tint-tryjobs-access.
Change-Id: Ib9541dbc36ec08d3b90850808a1d118926f2e110
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/25061
Reviewed-by: dan sinclair <dsinclair@chromium.org>
Based off of the configs used in Dawn
BUG=tint:1
Change-Id: Ie6d028dd0c0ae4ce77fa689a3e080b91afd56f83
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/23800
Reviewed-by: dan sinclair <dsinclair@google.com>
Ryan Harrison
Yiwei Zhang
dan sinclair
dan sinclair