You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by Eugene Koontz <ek...@hiro-tan.org> on 2012/06/13 02:05:28 UTC
Giraph trunk on builds.apache.org
There's a problem with the trunk build:
It's not passing -Phadoop_trunk to maven. See
https://builds.apache.org/job/Giraph-trunk-Commit/115/consoleFull
Notice that: "/home/jenkins/tools/maven/latest/bin/mvn clean verify" is
being executed, rather than
"/home/jenkins/tools/maven/latest/bin/mvn -Phadoop_trunk clean verify"
Paolo, I believe you are the person who knows how to configure Apache's
Jenkins? I'm happy to help if I you'd like.
-Eugene
Re: Giraph trunk on builds.apache.org
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 6/15/12 10:19 AM, Hyunsik Choi wrote:
> I've found why the unit tests were failed.
> The fails ware caused by "Address already in use" exceptions as you can see
> the full logs.
> This is because the multiple post-commit tests were executed on the same
> machine simulateneously.
> To avoid this problem, I changed the tied servers. Now, they work.
>
> --
> Hyunsik Choi
>
>
Wow! Nice find, Hyunsik. This is great to see. I'd like to help you
diagnose these type of problems in the future.
Sometimes, though, I have a hard time finding out why builds failed.
For example, this build failed:
https://builds.apache.org/job/giraph-trunk-hadoop-0.23/1/consoleText
The only indication that it failed is:
"Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to
FAILURE
Finished: FAILURE"
(But at line 4174, it says, "BUILD SUCCESS" - very strange.)
I saved the above here, in case Jenkins deletes it:
https://gist.github.com/2939071
-Eugene
Re: Giraph trunk on builds.apache.org
Posted by Hyunsik Choi <hy...@apache.org>.
I've found why the unit tests were failed.
The fails ware caused by "Address already in use" exceptions as you can see
the full logs.
This is because the multiple post-commit tests were executed on the same
machine simulateneously.
To avoid this problem, I changed the tied servers. Now, they work.
--
Hyunsik Choi
On Wed, Jun 13, 2012 at 11:31 PM, Eugene Koontz <ek...@hiro-tan.org>wrote:
> On 6/12/12 7:30 PM, Hyunsik Choi wrote:
> > Giraph-trunk is for default maven profile.
> > There is another jenkins project for hadoop-trunk as you can see the
> below
> > link:
> > https://builds.apache.org/view/G-L/view/Giraph/.
> > (but, it seems not working due to missing snapshot)
> >
> > In the above link, jenkins says that most profiles (including.,
> hadoop-1.0
> > and 0.20.203) incurs unittest errors
> > after GIRAPH-201. However, in my machine, their unittests are all passed.
> >
> > --
> > Hyunsik Choi
> >
>
> Thank you Hyunsik, you are right: the -P profile flags are being set as
> they should be for the Hadoop trunk build:
>
>
> https://builds.apache.org/view/G-L/view/Giraph/job/giraph-trunk-hadoop-trunk/3/console
>
> (mvn -Phadoop_trunk clean verify)
>
> I get the same results as you with regard to testing - they work on my
> local machine, but there's various errors in all Jenkins profiles except
> hadoop-0.23.
>
> I think we should try to get the hadoop-1.0 profile to turn blue as our
> first Jenkins-related priority.
>
> -Eugene
>
>
Re: Giraph trunk on builds.apache.org
Posted by Eugene Koontz <ek...@hiro-tan.org>.
On 6/12/12 7:30 PM, Hyunsik Choi wrote:
> Giraph-trunk is for default maven profile.
> There is another jenkins project for hadoop-trunk as you can see the below
> link:
> https://builds.apache.org/view/G-L/view/Giraph/.
> (but, it seems not working due to missing snapshot)
>
> In the above link, jenkins says that most profiles (including., hadoop-1.0
> and 0.20.203) incurs unittest errors
> after GIRAPH-201. However, in my machine, their unittests are all passed.
>
> --
> Hyunsik Choi
>
Thank you Hyunsik, you are right: the -P profile flags are being set as
they should be for the Hadoop trunk build:
https://builds.apache.org/view/G-L/view/Giraph/job/giraph-trunk-hadoop-trunk/3/console
(mvn -Phadoop_trunk clean verify)
I get the same results as you with regard to testing - they work on my
local machine, but there's various errors in all Jenkins profiles except
hadoop-0.23.
I think we should try to get the hadoop-1.0 profile to turn blue as our
first Jenkins-related priority.
-Eugene
Re: Giraph trunk on builds.apache.org
Posted by Hyunsik Choi <hy...@apache.org>.
Giraph-trunk is for default maven profile.
There is another jenkins project for hadoop-trunk as you can see the below
link:
https://builds.apache.org/view/G-L/view/Giraph/.
(but, it seems not working due to missing snapshot)
In the above link, jenkins says that most profiles (including., hadoop-1.0
and 0.20.203) incurs unittest errors
after GIRAPH-201. However, in my machine, their unittests are all passed.
--
Hyunsik Choi
On Wed, Jun 13, 2012 at 9:05 AM, Eugene Koontz <ek...@hiro-tan.org> wrote:
> There's a problem with the trunk build:
>
> It's not passing -Phadoop_trunk to maven. See
>
> https://builds.apache.org/job/Giraph-trunk-Commit/115/consoleFull
>
> Notice that: "/home/jenkins/tools/maven/latest/bin/mvn clean verify" is
> being executed, rather than
>
> "/home/jenkins/tools/maven/latest/bin/mvn -Phadoop_trunk clean verify"
>
> Paolo, I believe you are the person who knows how to configure Apache's
> Jenkins? I'm happy to help if I you'd like.
>
> -Eugene
>