Commit 685ed42
authored
Allow clang and gcc builds for
Summary: Allow clang and gcc builds for
`src/e2e_test/vizier/planner:planner_test`
As far as I can tell, there isn't a bazel config that matches the tags
of the `src/e2e_test/vizier/planner:planner_test` target. This change
removes the tag preventing clang builds since they appear to run without
problems. In addition to this, a `vispb` proto change was missing from
the earlier differential flamegraph work. This prevented the
`planner_test` from running properly (see comment for more details).
Relevant Issues: N/A
Type of change: /kind bugfix
Test Plan: Verified gcc and clang builds work
- [x] `bazel test --config clang
src/e2e_test/vizier/planner:planner_test` is successful
- [x] `bazel test -c opt --config gcc
src/e2e_test/vizier/planner:planner_test` is successful
---------
Signed-off-by: Dom Del Nano <[email protected]>src/e2e_test/vizier/planner:planner_test (#2077)1 parent e20880f commit 685ed42
File tree
6 files changed
+218
-126
lines changed- src
- api/proto/vispb
- common/exec
- e2e_test/vizier/planner
- ui/src/types/generated
6 files changed
+218
-126
lines changedSome generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
458 | 458 | | |
459 | 459 | | |
460 | 460 | | |
| 461 | + | |
| 462 | + | |
| 463 | + | |
461 | 464 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
27 | 33 | | |
28 | | - | |
| 34 | + | |
29 | 35 | | |
30 | 36 | | |
31 | 37 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
28 | | - | |
29 | 27 | | |
30 | 28 | | |
31 | 29 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments