You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by steveloughran <gi...@git.apache.org> on 2015/11/18 23:26:21 UTC
[GitHub] hadoop pull request: YARN-3477 timeline diagnostics
GitHub user steveloughran opened a pull request:
https://github.com/apache/hadoop/pull/47
YARN-3477 timeline diagnostics
YARN-3477 timeline diagnostics: add more details on why things are failing, including stack traces (at debug level sometimes)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/steveloughran/hadoop stevel/YARN-3477-timeline-diagnostics
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/47.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #47
----
commit 5278ac3de77e866e6528b5b6fb6f8d294c541a5f
Author: Steve Loughran <st...@hortonworks.com>
Date: 2015-04-23T14:18:26Z
YARN-3477 TimelineClientImpl swallows exceptions
commit 7a3701b66ef415ff8c5f9fdeec4ebe292d0eab75
Author: Steve Loughran <st...@hortonworks.com>
Date: 2015-04-24T12:03:09Z
YARN-3477 patch 002
# rethrowing runtime exception on timeout, but including the IOE as an inner exception
# using constant strings in the error messages
# clean up tests to (a) use those constant strings in tests, (b) throw the original exception on any mismatch, plus other improvements
commit 43b6b1fc126bff5b4be95bdd2fbab3bf686edde5
Author: Steve Loughran <st...@hortonworks.com>
Date: 2015-11-18T22:25:18Z
YARN-3277 make sure there's spaces; chop line > 80 chars wide
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
Re: [GitHub] hadoop pull request: YARN-3477 timeline diagnostics
Posted by Steve Loughran <st...@hortonworks.com>.
OK, I'm going to to conclude here that having github pull request -> emails is going to generate so much noise its unmanageable. The related JIRA, https://issues.apache.org/jira/browse/YARN-3477 , does have the same text, so that should be enough.
Owen: is there a way to turn off the automatic email-from-pull-request feature?
> On 18 Nov 2015, at 22:26, steveloughran <gi...@git.apache.org> wrote:
>
> GitHub user steveloughran opened a pull request:
>
> https://github.com/apache/hadoop/pull/47
>
> YARN-3477 timeline diagnostics
>
> YARN-3477 timeline diagnostics: add more details on why things are failing, including stack traces (at debug level sometimes)
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/steveloughran/hadoop stevel/YARN-3477-timeline-diagnostics
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/hadoop/pull/47.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #47
>
> ----
> commit 5278ac3de77e866e6528b5b6fb6f8d294c541a5f
> Author: Steve Loughran <st...@hortonworks.com>
> Date: 2015-04-23T14:18:26Z
>
> YARN-3477 TimelineClientImpl swallows exceptions
>
> commit 7a3701b66ef415ff8c5f9fdeec4ebe292d0eab75
> Author: Steve Loughran <st...@hortonworks.com>
> Date: 2015-04-24T12:03:09Z
>
> YARN-3477 patch 002
> # rethrowing runtime exception on timeout, but including the IOE as an inner exception
> # using constant strings in the error messages
> # clean up tests to (a) use those constant strings in tests, (b) throw the original exception on any mismatch, plus other improvements
>
> commit 43b6b1fc126bff5b4be95bdd2fbab3bf686edde5
> Author: Steve Loughran <st...@hortonworks.com>
> Date: 2015-11-18T22:25:18Z
>
> YARN-3277 make sure there's spaces; chop line > 80 chars wide
>
> ----
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastructure@apache.org or file a JIRA ticket
> with INFRA.
> ---
>