Issues build OpenJDK8

Mani Sarkar sadhak001 at gmail.com
Sun Feb 8 11:24:19 UTC 2015


Good observations and thanks.

There is a check to see if the binaries are present don't download - I
noticed, the workspace gets cleared at each build.

Which could be the reason behind the re-downloads, and the issues you
mentioned. As I said it was the same script for OpenJDK9 and worked without
any issues.

I'll find out about workspace clearance as its not necessary in our case -
maybe once in a while.

Cheers,
Mani

On Sun, Feb 8, 2015 at 10:57 AM, Magnus Ihse Bursie <
magnus.ihse.bursie at oracle.com> wrote:

> I also noted that you download the source for external dependencies
> directly from the upstream website for each build, and rebuild it from
> scratch.
>
> I would recommend that you build it once locally and then use that
> pre-built binary. Apart from putting an extra load on often underfunded
> open source projects, you are at the mercy of all kinds of network
> troubles. In fact, my guess is that the intermittent failure you saw might
> be due to an intermittent failure in the download or build of alsa.
>
> /Magnus
>
> 7 feb 2015 kl. 23:43 skrev Mani Sarkar <sadhak001 at gmail.com>:
>
> Hi Magnus,
>
> Thanks for getting back to me so quickly.
>
> Its strange on two counts
> - --with-alsa-lib wasn;t needed for OpenJDK9 since ever, it builds find
> there
> - after I sent out the mail and triggered the build, it ran successfully
> which you just pointed out.
>
> But for sanity reasons, I have added the --with-alsa-lib option to the
> configure and made it point to the lib for alsa and I'll wait to see what
> happens to the build.
>
> Thanks again.
>
> Cheers,
> Mani
>
>
> On Sat, Feb 7, 2015 at 9:10 PM, Magnus Ihse Bursie <
> magnus.ihse.bursie at oracle.com> wrote:
>
>> It seems your configure script only gets sent a --with-alsa-include and
>> not an --with-alsa-lib. I'm not sure this is the problem but it looks
>> wrong.
>>
>> I couldn't find any issues with the log I looked at. It seemed to compile
>> normally. (
>> https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/openjdk-1.8-linux-x86_64/107/consoleFull
>> )
>>
>> /Magnus
>>
>> 7 feb 2015 kl. 13:42 skrev Mani Sarkar <sadhak001 at gmail.com>:
>>
>> Hi all,
>>
>> Although we are on OpenJDK9 and the AdoptOpenJDK build farms are already
>> producing binaries for it, we also have OpenJDK8 jobs that run
>> occasionally
>> and these have been failing due to the below reasons:
>>
>> ## Starting jdk*/usr/bin/ld: cannot find -lasound*
>> collect2: error: ld returned 1 exit status
>> gmake[2]: ***
>> [/scratch/jenkins/workspace/openjdk-1.8-linux-x86_64/build/linux-x86_64-normal-server-release/jdk/lib/amd64/libjsoundalsa.so]
>> Error 1
>> gmake[2]: *** Waiting for unfinished jobs....
>> gmake[1]: *** [libs-only] Error 2
>> make: *** [jdk-only] Error 2
>> Package test output into archives...
>> /scratch/jenkins/workspace/openjdk-1.8-linux-x86_64
>> Removing existing (old) artefact:
>> openjdk-1.8-linux-x86_64-jcov-testresults.tar.gz
>> Tarring and zipping the 'testoutput' folder into artefact:
>> openjdk-1.8-linux-x86_64-jcov-testresults.tar.gz
>> tar: testoutput: Cannot stat: No such file or directory
>> tar: Exiting with failure status due to previous errors
>> Moving artefact openjdk-1.8-linux-x86_64-jcov-testresults.tar.gz into
>> /scratch/jenkins/workspace/openjdk-1.8-linux-x86_64
>> Archiving artifacts
>> ERROR: No artifacts found that match the file pattern
>> "openjdk-1.8-linux-x86_64-105.tar.gz". Configuration error?ERROR
>> <http://stacktrace.jenkins-ci.org/search?query=ERROR>:
>> ‘openjdk-1.8-linux-x86_64-105.tar.gz’ doesn’t match anything
>> Build step 'Archive the artifacts' changed build result to FAILURE
>>
>>
>> Even though asound has been installed at the start of the process.
>>
>> Here's the logs for more details -
>>
>> https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/openjdk-1.8-linux-x86_64/
>>
>> I could run the build in debug mode if the logs don't tell us enough.
>>
>> Cheers,
>> Mani
>>
>> --
>> @theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
>> <http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
>> (@adoptopenjdk & @adoptajsr programs)
>> *Meet-a-Project - *MutabilityDetector
>> <https://github.com/MutabilityDetector>*  |  **Bitbucket
>> <https://bitbucket.org/neomatrix369>* * |  **Github
>> <https://github.com/neomatrix369>* * |  **LinkedIn
>> <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
>> *Come to Devoxx UK 2015:* http://www.devoxx.co.uk/
>>
>> *Don't chase success, rather aim for "Excellence", and success will come
>> chasing after you!*
>>
>>
>
>
> --
> @theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
> <http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
> (@adoptopenjdk & @adoptajsr programs)
> *Meet-a-Project - *MutabilityDetector
> <https://github.com/MutabilityDetector>*  |  **Bitbucket
> <https://bitbucket.org/neomatrix369>* * |  **Github
> <https://github.com/neomatrix369>* * |  **LinkedIn
> <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
> *Come to Devoxx UK 2015:* http://www.devoxx.co.uk/
>
> *Don't chase success, rather aim for "Excellence", and success will come
> chasing after you!*
>
>


-- 
@theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
<http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
(@adoptopenjdk & @adoptajsr programs)
*Meet-a-Project - *MutabilityDetector
<https://github.com/MutabilityDetector>*  |  **Bitbucket
<https://bitbucket.org/neomatrix369>* * |  **Github
<https://github.com/neomatrix369>* * |  **LinkedIn
<http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
*Come to Devoxx UK 2015:* http://www.devoxx.co.uk/

*Don't chase success, rather aim for "Excellence", and success will come
chasing after you!*



More information about the build-dev mailing list