[ 
https://issues.apache.org/jira/browse/AURORA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257162#comment-15257162
 ] 

John Sirois commented on AURORA-1682:
-------------------------------------

Another transient issue see 
[here|https://builds.apache.org/job/aurora-packaging-nightly/280/console]:
{noformat}
...
Preparing to unpack .../openjdk-8-jdk_8u91-b14-0ubuntu4~14.04_amd64.deb ...
Unpacking openjdk-8-jdk:amd64 (8u91-b14-0ubuntu4~14.04) ...
Selecting previously unselected package policykit-1-gnome.
Preparing to unpack .../policykit-1-gnome_0.105-1ubuntu4_amd64.deb ...
Unpacking policykit-1-gnome (0.105-1ubuntu4) ...
Selecting previously unselected package tcpd.
Preparing to unpack .../tcpd_7.6.q-25_amd64.deb ...
Unpacking tcpd (7.6.q-25) ...
Selecting previously unselected package gdisk.
Preparing to unpack .../gdisk_0.8.8-1ubuntu0.1_amd64.deb ...
Unpacking gdisk (0.8.8-1ubuntu0.1) ...
Processing triggers for initramfs-tools (0.103ubuntu4.3) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for ca-certificates (20160104ubuntu0.14.04.1) ...
Updating certificates in /etc/ssl/certs... sed: error while loading shared 
libraries: libdl.so.2: failed to map segment from shared object: Permission 
denied
dpkg: error processing package ca-certificates (--unpack):
 subprocess installed post-installation script returned error exit status 127
Processing triggers for ureadahead (0.100.0-16) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Processing triggers for udev (204-5ubuntu20.19) ...
Processing triggers for libglib2.0-0:amd64 (2.40.2-0ubuntu1) ...
Errors were encountered while processing:
 ca-certificates
E: Sub-process /usr/bin/dpkg returned an error code (1)
The command '/bin/sh -c add-apt-repository ppa:openjdk-r/ppa -y   && apt-get 
update   && apt-get install -y openjdk-8-jdk   && update-alternatives --set 
java /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java' returned a non-zero code: 
100
Build step 'Execute shell' marked build as failure
Skipped archiving because build is not successful
Sending e-mails to: [email protected]
Finished: FAILURE
{noformat}

I've personally used the fix (a big hammer) suggested by [~vinodkone] for Mesos 
[here|https://issues.apache.org/jira/browse/MESOS-2233] in the 
[Thrift-precommit job|https://builds.apache.org/job/Thrift-precommit].


> https://builds.apache.org/job/aurora-packaging-nightly is broken
> ----------------------------------------------------------------
>
>                 Key: AURORA-1682
>                 URL: https://issues.apache.org/jira/browse/AURORA-1682
>             Project: Aurora
>          Issue Type: Bug
>          Components: Continuous Integration, Packaging
>            Reporter: John Sirois
>            Assignee: John Sirois
>
> It looks like 
> https://git1-us-west.apache.org/repos/asf?p=aurora-packaging.git;a=commit;h=d5d41691c476fdfe32a595efcd53fc3a007d4d9e
>  broke the nightly CI.  That CI uses a custom version, namely {{version=$(cat 
> .auroraversion).$(date +%Y.%m.%d)}}, which breaks CI with:
> {noformat}
> ...
> -rwxrwxr-x root/root     13218 2016-04-22 22:43 
> apache-aurora-0.13.1snapshot.2016.04.25/src/test/sh/org/apache/aurora/e2e/test_end_to_end.sh
> -rwxrwxr-x root/root      5275 2016-04-22 22:43 
> apache-aurora-0.13.1snapshot.2016.04.25/src/test/sh/org/apache/aurora/e2e/test_kerberos_end_to_end.sh
> -rw-rw-r-- root/root      1483 2016-04-22 22:43 
> apache-aurora-0.13.1snapshot.2016.04.25/src/test/sh/org/apache/aurora/e2e/validate_serverset.py
> + STATUS=0
> + '[' 0 -ne 0 ']'
> + cd apache-aurora-0.13.1-SNAPSHOT
> /var/tmp/rpm-tmp.ZAuzps: line 35: cd: apache-aurora-0.13.1-SNAPSHOT: No such 
> file or directory
> error: Bad exit status from /var/tmp/rpm-tmp.ZAuzps (%prep)
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.ZAuzps (%prep)
> make: *** [rpm] Error 1
> Build step 'Execute shell' marked build as failure
> Skipped archiving because build is not successful
> Sending e-mails to: [email protected]
> Finished: FAILURE
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to