-
Notifications
You must be signed in to change notification settings - Fork 588
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
Weird error message when there where two targets with the same name #1375
Comments
I second that. Just got the same error when we had the same target added in different branches. While the merge went fine without conflicts, the build (of course failed). Explicitly naming the task should make debugging such cases easier. |
Please send a fix. It's probably a dictionary add call failing somewhere.
Am 27.03.2017 20:01 schrieb "Michel Bretschneider" <notifications@github.com
…:
I second that. Just got the same error when we had the same target added
in different branches. While the merge went fine without conflicts, the
build (of course failed). Explicitly naming the task should make debugging
such cases easier.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1375 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADgNAqWsQqk-Af6I5YOJmNs3CJP1xLOks5rp8xcgaJpZM4J6QPC>
.
|
Bread and butter solution: just throw an exception and provide the name of the duplicate target. If there is a more sophisticated way of croaking in FAKE just give me a hint. |
Description
While writing a FAKE script I got a rather weird error message when there where two targets with the same name.
Repro steps
How did I get it wrong? Well I wrote the following:
Expected behavior
I would have expected FAKE to report that target was already declared or something along those lines.
Actual behavior
This is the output I got:
Related information
The text was updated successfully, but these errors were encountered: