build: add mdc prebuilt theme to karma legacy tests #16965
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
devversion
added
pr: merge safe
target: patch
googlebot
added
the
cla: yes
Adds the MDC prebuilt theme to the karma legacy tests. This is consistent with what we did for the Bazel tests. It can cause unexpected differences and confusion when debugging tests in both Bazel and the legacy job (different visual output).
devversion
force-pushed
the
build/add-prebuilt-theme-karma-legacy
branch
from
baa1eab to
667d33c
Compare
josephperrott
added
pr: lgtm
action: merge
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds the MDC prebuilt theme to the karma legacy tests. This is
consistent with what we did for the Bazel tests. It can cause
unexpected differences and confusion when debugging tests in
both Bazel and the legacy job (different visual output).