[
https://issues.apache.org/jira/browse/HADOOP-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-6110:
---
Priority: Critical (was: Major)
Assignee: Giridharan Kesavan
> test-patch takes 45
[
https://issues.apache.org/jira/browse/HADOOP-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-6110:
---
Component/s: build
> test-patch takes 45
the hadoop-commons take 10 minutes to execute, but test
patch takes like nearly 45-50 minutes.
> test-patch takes 45min!
> ---
>
> Key: HADOOP-6110
> URL: https://issues.apache.org/jira/browse/HADOOP-6110
>
test-patch takes 45min!
---
Key: HADOOP-6110
URL: https://issues.apache.org/jira/browse/HADOOP-6110
Project: Hadoop Common
Issue Type: Improvement
Components: test
Reporter: Amar Kamat
The runtime
[
https://issues.apache.org/jira/browse/HADOOP-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley reassigned HADOOP-6077:
---
Assignee: Giridharan Kesavan
> test-patch target does not validate that forrest docs
test-patch target does not validate that forrest docs are built correctly
-
Key: HADOOP-6077
URL: https://issues.apache.org/jira/browse/HADOOP-6077
Project: Hadoop Core
may cause this.
I just cannot reproduce the error on my linux box.
can anyone give me an environment setting (steps) to reproduce this error?
> hdfsproxy tests fails test patch builds.
> -
>
> Key: HADOOP-6007
>
at
org.apache.hadoop.hdfsproxy.TestHdfsProxy.testHdfsProxyInterface(TestHdfsProxy.java:224)
> hdfsproxy tests fails test patch builds.
> -
>
> Key: HADOOP-6007
> URL: https://issues.apache.org/jira
hdfsproxy tests fails test patch builds.
-
Key: HADOOP-6007
URL: https://issues.apache.org/jira/browse/HADOOP-6007
Project: Hadoop Core
Issue Type: Bug
Components: contrib/hdfsproxy
http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/703/])
. Add parameters java5.home and forrest.home to the ant commands in
test-patch.sh. (Giridharan Kesavan via szetszwo)
> ant test-patch does not work
>
>
> Key: HADOOP-4948
>
was with the environment variables on my machine. Thanks
Giri for helping it out.
> ant test-patch does not work
>
>
> Key: HADOOP-4948
> URL: https://issues.apache.org/jira/browse/HADOOP-4948
>
ssue on the trunk, even with empty patch.
> ant test-patch does not work
>
>
> Key: HADOOP-4948
> URL: https://issues.apache.org/jira/browse/HADOOP-4948
> Project: Hadoop Core
> Issue Type:
trunk. Thanks, Giri!
If HADOOP-4920 is committed to 0.20, this one also should be.
> ant test-patch does not work
>
>
> Key: HADOOP-4948
> URL: https://issues.apache.org/jira/browse/HADOOP-4948
> Pr
Assignee: Giridharan Kesavan
Hadoop Flags: [Reviewed]
+1 patch looks good.
> ant test-patch does not work
>
>
> Key: HADOOP-4948
> URL: https://issues.apache.org/jira/browse/HADOOP-4948
> Pr
7 AM:
---
I'm able to reproduce the failure.
After the the fix for HADOOP-4920, the package target depends on docs target,
with inturn depends on forrest.home and java5.home
When we call the test-patch target through ant though, we pass the forrest.home
& java5.home the test-pa
e fix for HADOOP-4920, the package target depends on docs target,
with inturn depends on forrest.home and java5.home
When we call the test-patch target through ant though we pass the forrest.home
& java5.home the test-patch.sh script doesn't seem to pass the 2 env variables
when calli
*/home/tsz/tmp/trunkJavacWarnings.txt*
Thanks,
Giri
> ant test-patch does not work
>
>
> Key: HADOOP-4948
> URL: https://issues.apache.org/jira/browse/HADOOP-4948
> Project: Hadoop Core
> Issue Type:
ce, could you please paste here the reason for the failure
from the log file */home/tsz/tmp/trunkJavacWarnings.txt*
Thanks,
Giri
> ant test-patch does not work
>
>
> Key: HADOOP-4948
> URL: https://issues.apache.org
ant test-patch does not work
Key: HADOOP-4948
URL: https://issues.apache.org/jira/browse/HADOOP-4948
Project: Hadoop Core
Issue Type: Bug
Components: scripts
Affects Versions: 0.21.0
http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/698/])
> After introduction of ivy ant test-patch always returns -1 score
>
>
> Key: HADOOP-4878
> URL: https://issues.apache.org/jira
!
> After introduction of ivy ant test-patch always returns -1 score
>
>
> Key: HADOOP-4878
> URL: https://issues.apache.org/jira/browse/HADOOP-4878
> Project: Hadoop Cor
; Components: build
>Reporter: Sreekanth Ramakrishnan
>Assignee: Giridharan Kesavan
>Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-4878.patch
>
>
> After dependency management is moved to ivy :
d lib dir's to
.eclipse.templates/.classpath file and
added the same path to test-patch.sh script.
This patch adds changes to the patch testing script itself. Hence this patch
cannot be tested using the test-patch target.
I ve tested is manually and it works just fine.
[exec]
Kesavan
i've disabled patch testing until this is resolved. Giri is looking at the
issue now.
> After introduction of ivy ant test-patch always returns -1 score
>
>
> Key: HADOOP-4878
>
[
https://issues.apache.org/jira/browse/HADOOP-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656911#action_12656911
]
Sreekanth Ramakrishnan commented on HADOOP-4878:
Output of ant test-p
After introduction of ivy ant test-patch always returns -1 score
Key: HADOOP-4878
URL: https://issues.apache.org/jira/browse/HADOOP-4878
Project: Hadoop Core
Issue Type: Bug
Ant test-patch goal (and test/bin/test-patch.sh script) fails without warnings
if ANT_HOME environment variable is not set
--
Key: HADOOP-4870
[
https://issues.apache.org/jira/browse/HADOOP-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-4165:
Fix Version/s: (was: 0.19.0)
0.20.0
Not a blocker for 0.19
> test-pa
http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/615/])
> In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
> only
> --
>
> Key: HADOOP-4244
[
https://issues.apache.org/jira/browse/HADOOP-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-4244:
---
Assignee: Tsz Wo (Nicholas), SZE
> In "ant te
: [Reviewed]
Thanks Nigel for reviewing.
I just committed this.
> In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
> only
> --
>
> Key: HADOOP-4244
>
atch Available. This patch can't be tested
properly by Hudson since it modifies the script that Hudson runs.
> In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
> only
> --
> In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
> only
> --
>
> Key: HADOOP-4244
> URL: https://issues.apache
The patch passed Eclipse unit tests." ->
"+1 Eclipse tests. The patch retains Eclipse classpath integrity."
> In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
> only
>
and contrib tests
> In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
> only
> --
>
> Key: HADOOP-4244
> URL: https://issues.a
hile ago too. It could have been
much easier to spot this had Hudson explicitly pointed out the jars that were
missing/extra, saving us from iterating through the whole list of jars and
finding out the culprit.
> In "ant test-patch", runContribTestOnEclipseFiles should not be run
[
https://issues.apache.org/jira/browse/HADOOP-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-4258:
Component/s: test
> the test patch script should check for filenames that differ only in c
the test patch script should check for filenames that differ only in case
-
Key: HADOOP-4258
URL: https://issues.apache.org/jira/browse/HADOOP-4258
Project: Hadoop Core
4249 and submitted a patch for adding hsqldb.jar in the
eclipse templates. How can I test it locally?
> In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
> only
> --
[
https://issues.apache.org/jira/browse/HADOOP-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-4244:
Nicholas, the -1 comes from the eclipse plugin classpath check that someone put
into test-patch. At
bugs in runContribTests(). It gives a -1 even if there is
no tests fails. For example,
see
https://issues.apache.org/jira/browse/HADOOP-4242?focusedCommentId=12633545#action_12633545
> In "ant test-patch", runContribTestOnEclipseFiles should not be run
In "ant test-patch", runContribTestOnEclipseFiles should not be run on Hudson
only
--
Key: HADOOP-4244
URL: https://issues.apache.org/jira/browse/HADOOP-4244
http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/611/])
> test-patch can report the modifications found in the workspace along with the
> error message
> ---
>
> Key: HADOOP-3975
&g
Available)
I just committed this. Thanks, Rayma
> test-patch can report the modifications found in the workspace along with the
> error message
> ---
>
> Key: HADOOP-3975
>
e +1 (or otherwise) of core and contrib tests in
the test-patch output.
> test-patch should have a mode where developers can turn on running core and
> contrib tests.
> --
>
>
[
https://issues.apache.org/jira/browse/HADOOP-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632574#action_12632574
]
Arun C Murthy commented on HADOOP-4215:
---
'ant test-patch test' ?
test-patch should have a mode where developers can turn on running core and
contrib tests.
--
Key: HADOOP-4215
URL: https://issues.apache.org/jira/browse/HADOOP-4215
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632097#action_12632097
]
Ramya R commented on HADOOP-3975:
-
Ran test-patch locally, here are the results:
[
non-zero. Ramya, can you update the
patch?
Enis, regarding your comments, please file a new Jira. I think this patch
makes the current system a little better. Your suggestion may require a much
bigger change.
> test-patch can report the modifications found in the workspace along with the
test-patch script is showing questionable number of Javac warnings
--
Key: HADOOP-4165
URL: https://issues.apache.org/jira/browse/HADOOP-4165
Project: Hadoop Core
Issue Type
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630162#action_12630162
]
Enis Soztutar commented on HADOOP-3975:
---
I think, test-patch should be able to
sage is automatically generated.
> test-patch can report the modifications found in the workspace along with the
> error message
> ---
>
> Key: HADOOP-3975
>
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627559#action_12627559
]
Chris Douglas commented on HADOOP-3975:
---
Shouldn't test-patch return no
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya R updated HADOOP-3975:
Status: Patch Available (was: Open)
> test-patch can report the modifications found in the worksp
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya R updated HADOOP-3975:
Component/s: (was: build)
test
Fix Version/s: 0.19.0
> test-patch can rep
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya R updated HADOOP-3975:
Attachment: hadoop-3975-v1.txt
Updated patch submitted.
> test-patch can report the modifications fo
patch that applies.
Thanks!
> test-patch can report the modifications found in the workspace along with the
> error message
> ---
>
> Key: HADOOP-3975
>
the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
&
Available)
I just committed this. Thanks Ramya!
PS : I am trying to assign this issue to you, but unable to find your name in
the drop down box.
> Place the new findbugs warnings introduced by the patch in the /tmp directory
> when "ant test-pa
in the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOO
y the ant
execution order, which I fixed in HADOOP-4023 by making javadoc depend on
compile.
> "ant test-patch" and "ant javadoc" are inconsistent
> ---
>
> Key: HADOOP-4024
> UR
atch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3098/console
This message is automatically generated.
> test-patch can report the modifications found in the workspace along with the
> err
d by Vinod.
> test-patch can report the modifications found in the workspace along with the
> error message
> ---
>
> Key: HADOOP-3975
> URL: https://issues.apache
http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> test-patch target not working on hudson.zones.apache.org due to HADOOP-3480
> ---
>
> Key: HADOOP-3653
> URL: https://issues.apa
You could store the output of "$SVN stat" in a variable and use
it, instead of running it two times.
> test-patch can report the modifications found in the workspace along with the
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya R updated HADOOP-3975:
Status: Patch Available (was: Open)
> test-patch can report the modifications found in the worksp
atch.
> test-patch can report the modifications found in the workspace along with the
> error message
> ---
>
> Key: HADOOP-3975
> URL: https://issues.apache.org/j
[
https://issues.apache.org/jira/browse/HADOOP-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramya R updated HADOOP-3975:
Attachment: test-patch1.txt
> test-patch can report the modifications found in the workspace along w
test-patch can report the modifications found in the workspace along with the
error message
---
Key: HADOOP-3975
URL: https://issues.apache.org/jira/browse/HADOOP-3975
the
newPatchFindbugsWarnings.xml file which we want to place in the ~/tmp
directory to help the developers easily find the file and to identify
the new findbugs warnings introduced by their patch.
> Place the new findbugs warnings introduced by the patch in the /tmp directory
> when "
Is newPatchFindbugsWarnings.html the html file mentioned here? If yes, it is
very useful.
I always diff the xml files manually and try to understand the xml findbugs
warnings, which is not quite convenient.
> Place the new findbugs warnings introduced by the patch in the /tmp directory
> when "ant tes
ut
don't know where to look. Putting them in PATCH_DIR puts them in with the
other results from other tools. Let me know if you see a better solution.
> Place the new findbugs warnings introduced by the patch in the /tmp directory
> whe
uild directory, which is why I asked if it has something to do with Hudson
> Place the new findbugs warnings introduced by the patch in the /tmp directory
> when &qu
This message is automatically generated.
> Place the new findbugs warnings introduced by the patch in the /tmp directory
> when "ant test-patch" is run.
> ---
>
>
indbugs warnings introduced by the patch in the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https
ugs warnings introduced by the patch in the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issu
html and .xml format
Is this a change to Hudson? For developers running test-patch locally, this
seems unnecessary.
> Place the new findbugs warnings introduced by the patch in the /tmp directory
> when "ant tes
tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
>
ngs introduced by the patch in the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache
tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
>
the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
&
tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
>
the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
&
tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
>
the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
>
the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
>
the /tmp directory
> when "ant test-patch" is run.
> ---
>
> Key: HADOOP-3966
> URL: https://issues.apache.org/jira/browse/HADOOP-3966
>
Place the new findbugs warnings introduced by the patch in the /tmp directory
when "ant test-patch" is run.
---
Key: HADOOP-3966
)
I just committed this to trunk and branch-0.18. Thanks Brice!
> test-patch target not working on hudson.zones.apache.org due to HADOOP-3480
> ---
>
> Key: HADOOP-3653
>
sage is automatically generated.
> test-patch target not working on hudson.zones.apache.org due to HADOOP-3480
> ---
>
> Key: HADOOP-3653
> URL: https://issues.apache.org/jira
0_v2.patch,
> fixHusondBreak3480_v3.patch, HADOOP-3653.patch
>
>
> HADOOP-3480 has broken the test-patch target run by the Hudson Hadoop-Patch
> job. This is causing all patches to get a -1 on contrib testing.
> Also, the message is very confusing now. This is what the console shows:
[
https://issues.apache.org/jira/browse/HADOOP-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-3653:
Status: Open (was: Patch Available)
> test-patch target not working on hudson.zones.apache.
[
https://issues.apache.org/jira/browse/HADOOP-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-3653:
Status: Patch Available (was: Open)
> test-patch target not working on hudson.zones.apache.
sole
This message is automatically generated.
> test-patch target not working on hudson.zones.apache.org due to HADOOP-3480
> ---
>
> Key: HADOOP-3653
> URL: https://issues.apache.org
[
https://issues.apache.org/jira/browse/HADOOP-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-3653:
--
Status: Patch Available (was: Open)
> test-patch target not working
[
https://issues.apache.org/jira/browse/HADOOP-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-3653:
--
Status: Open (was: Patch Available)
> test-patch target not working
; appeared in 3.1-rc1.
So this one should be the right. I'll try to find an old system to test it
tomorrow.
I'll also have to RTFM about Hudson :-/.
Thanks a lot for your help
> test-patch target not working on hudson.zones.apache
rectory
Note this host runs Solaris x86:
[hudson]> bash -version
GNU bash, version 3.00.16(1)-release (i386-pc-solaris2.10)
Copyright (C) 2004 Free Software Foundation, Inc.
> test-patch target not working on hudson.zones.apache.org due to HADOOP-3480
> --
bash differs ?
This new version do things in a bit different way. I hope it will fix that
bug... Thanks for your patience.
> test-patch target not working on hudson.zones.apache.org due to HADOOP-3480
> ---
>
>
l failing:
hudson> DECLARED_JARS+=' '$(cd "${SUPPORT_DIR}"; find lib -name '*.jar')
-bash: DECLARED_JARS+= lib/rat-0.5.1.jar: No such file or directory
> test-patch target not working
1 - 100 of 122 matches
Mail list logo
