[
https://issues.apache.org/jira/browse/HADOOP-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582032#action_12582032
]
Hadoop QA commented on HADOOP-3087:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12378557/patch-3087.txt
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2049/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2049/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2049/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2049/console
This message is automatically generated.
> JobInfo session object is not refreshed in loadHistory.jsp if same job is
> accessed again.
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-3087
> URL: https://issues.apache.org/jira/browse/HADOOP-3087
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.17.0
>
> Attachments: patch-3087.txt
>
>
> JobInfo object is not refreshed in loadHistory.jsp if same job is accessed
> again. In loadhistory.jsp, the jobInfo object is stored as session
> attribute. And if the same job is accessed again, the object is not
> refreshed. This becomes a problem if first time the object accessed was
> during job running and it doesnt refresh even after completing the job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
