Team… It would be nice if this can be fixed quickly. This type of situation is holding me ( and I assume a lot of other developers) up.
In the future can we try to be more vigilant about running the tests before merging into the trunk? With approaching deadlines, no one can afford to be waiting around for issues like this to be fixed… especially when they could have been prevented in the first place. I am not a committer but I can’t imagine that this preventative measure would take that much time away from your other tasks. On that note, by failing to take the time and run the tests and then causing this issue, you most likely have created additional work for yourself - assuming you are involved in fixing the issue. Rob On Nov 19, 2014, at 10:51 AM, John Speidel <[email protected]> wrote: > Has been failing since: > AMBARI-8382 <https://issues.apache.org/jira/browse/AMBARI-8382> Configs: > Dashboard > Config History custom date option issues. (atkach) > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
