Great catch. It looks like I missed to test this combination ('make check'
does not trigger this one). Does it mean that jenkins jobs do more than
make check?

I will fix it.

Waldek

On Wed, Dec 21, 2016 at 4:39 AM, Nadav Har'El <[email protected]> wrote:

>
> On Wed, Dec 21, 2016 at 9:59 AM, Nadav Har'El <[email protected]> wrote:
>
>> On Wed, Dec 21, 2016 at 9:41 AM, <[email protected]> wrote:
>>
>>> See <http://jenkins.cloudius-systems.com:8080/job/osv-build/1157/changes
>>> >
>>>
>>>
>> Build (and test) run #1157 failed because it did not include the apps/
>> update. Not great (no bisectability), but we can live with it.
>>
>> But #1158, with the apps/ update, is also failing, in a different way:
>> http://jenkins.cloudius-systems.com:8080/job/osv-build/lastBuild/console
>>
>> It turns out the command "scripts/build image=java-tests,openjdk8-fedora"
>> crashes while uploading the files to the image:
>>
>> ...
>> Adding /usr/share/javazi/Europe/Lisbon...
>> Adding /usr/share/javazi/America/Miquelon...
>> Link /usr/lib/jvm/java to java-1.8.0-openjdk-1.8.0.111-3.b16.fc26.x86_64
>> ...
>> terminate called after throwing an instance of 'std::system_error'
>>   what():  symlink: File exists
>> Aborted
>>
>> Why do we try to create a link for /usr/lib/jvm/java twice? Does this
>> link appear in two separate modules' usr.manifest?
>>
>
> It seems it's not that we have two links for java, but rather that we put
> files in /usr/lib/jvm/java, e.g.,
> Adding /usr/lib/jvm/java/jre/lib/zi/Antarctica/Palmer...
>
> and also in java-1.8.0-openjdk-1.8.0.111-3.b16.fc26.x86_64:
>
> Adding /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-3.b16.fc26.
> x86_64/jre/lib/amd64/libjsdt.so...
>
> So now /usr/lib/jvm/java and /usr/lib/jvm/java-1.8.0-
> openjdk-1.8.0.111-3.b16.fc26.x86_64 are two independent directories - and
> one can't be made a link to the other.
>
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to