Skip to content

Conversation

@bripeticca
Copy link
Contributor

Currently branched off of swb/diagnosticcodesnippet.

* Built tentative test class SwiftBuildSystemOutputParser to
  handle the compiler output specifically
* Added a handleDiagnostic method to possibly substitute the
  emitEvent local scope implementation of handling a
  SwiftBuildMessage diagnostic
* the flag `appendToOutputStream` helps us to determine whether
  a diagnostic is to be emitted or whether we'll be emitting
  the compiler output via OutputInfo
* separate the emitEvent method into the SwiftBuildSystemMessageHandler
* Remove taskStarted outputStream emissions
* Propagate exception if unable to find path
The TaskDataBuffer introduces some extra complexity in its
handling of various buffers we'd actually like to track and
emit, rather than ignore.

We will keep multiple buffers depending on the information we
have available i.e. whether there's an existing task signature
buffer, taskID buffer, targetID buffer, or simply a global
buffer.
If there is no command line display strings available for a failed
task, we should demote this message to info-level to avoid cluttering
the output stream with messages that may not be incredibly helpful.

To consider here: if this is the only error, we should be able to expose
this as an error and perhaps omit "<no command line>".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant