-
Notifications
You must be signed in to change notification settings - Fork 12k
fix(@angular-devkit/build-angular): should not log duplicate messages #11628
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
Conversation
Hi, can you give me some context about the problem you are fixing? A way for me to see it happening would be important as well. |
@filipesilva , yes it's for |
I tried adding an error to an existing project, then introducing your changes, and I could still see duplicated error messages. Can you show me what do you see before and after your changes? Edit: I noticed now that while there is still some duplication, it is less than before. |
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.
Can you change the commit message to fix(@angular-devkit/build-angular): should not log duplicate messages
please? (build_angular
-> build-angular
)
@@ -240,6 +240,9 @@ const eventReporter: any = function (this: any, baseReporterDecorator: any) { | |||
failureCb && failureCb(); | |||
} | |||
} | |||
|
|||
// avoid duplicate failure message | |||
this.specFailure = (_browser: any, result: any) => {}; |
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.
This can be just this.specFailure = () => {};
, and the same applies to the other ones.
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.
done, thanks
hi @filipesilva, right now, with these changes, you will still see some duplicate, as these is also another reporter |
@filipesilva could you restart all the CI tests? seems all of them aren't triggered |
I will close and reopen to see if the CI can be restarted. |
LGTM, thanks for this fix! |
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. |
Should not log duplicate messages for
specFailure
andonRunComplete
, as they all have been handled by thebaseReporter