-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add emission of TestSubtaskEvents #5816
Add emission of TestSubtaskEvents #5816
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5816 +/- ##
==========================================
+ Coverage 71.00% 71.05% +0.04%
==========================================
Files 438 440 +2
Lines 16497 16532 +35
==========================================
+ Hits 11714 11746 +32
- Misses 3921 3923 +2
- Partials 862 863 +1
Continue to review full report at Codecov.
|
@@ -370,6 +370,11 @@ func (ev *eventHandler) handleExec(event *proto.Event) { | |||
ev.stateLock.Lock() | |||
ev.state.BuildState.Artifacts[be.Artifact] = be.Status | |||
ev.stateLock.Unlock() | |||
case *proto.Event_TestEvent: | |||
te := e.TestEvent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why we need these intermediate vars?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't think we do, this is mostly just a result of me copying from the previous event API 😅 I can make a follow up PR to clean this up a bit!
Fixes: #5784
Related: #5423
Description
Adds emission of
TestSubtaskEvent
s when tests start, finish, or failUser facing changes (remove if N/A)
Users can now see events that correlate to start, failure, and finish of tests in skaffold
Follow-up Work (remove if N/A)
Put more detail in these events. The initial definition doesn't have much meta info about the test running, but I'd like to update it with more information.