[Integrated Swift Driver] Do not create CompilerOutputParsers for swift-frontend jobs #2850
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
artemcm
requested review from
abertelrud,
aciidgh,
friedbunny and
neonichu
as code owners
|
@swift-ci please smoke test |
DougGregor
approved these changes
Aug 6, 2020
|
I filed https://bugs.swift.org/browse/SR-13351 to make the Swift frontend do what I thought it did |
…ft-frontend jobs The swift-frontend currently does not support parseable output, therefore, the parsers here are not needed. The presence of these parsers also leads to these jobs to be skipped from being reported on in the LLBuild status line printing. Resolves rdar://66594405
artemcm
force-pushed
the
DontParseWhatYouCantRead
branch
from
e40d4f6 to
da0aa69
Compare
|
@swift-ci please smoke test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The swift-frontend currently does not support parseable output, therefore, the parsers here are not needed.
The presence of these parsers also leads to these jobs to be skipped from being reported on in the LLBuild status line printing.
Resolves rdar://66594405