Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 518231

Summary:	Build failures in pack200 steps of rap-head-tools job
Product:	[RT] RAP	Reporter:	Markus Knauer <mknauer>
Component:	Releng	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	P3	CC:	ivan
Version:	3.2
Target Milestone:	3.2
Hardware:	All
OS:	All
Whiteboard:

Description Markus Knauer

2017-06-14 07:03:26 EDT

Since a couple of weeks we see a lot of build failures on our RAP Hudson instance at [1], especially in on of our jobs that builds the RAP Tools [2]. It is about one out of ten builds that is successful, interestingly this seems to depend on server load or on other external reasons, because it happened in the past that a second or a third build from the same Git commit hash and with an unmodified Hudson job configuration runs successful, whereas other builds with the very same input fail.

As a result we weren't able to deliver a signed Oxygen RC2 build for RAP Tools.

After many retries we got one successful build for RC3 last week.

This week it seems worse... we need to deliver an RC4 build, but had still no luck.


[1] https://hudson.eclipse.org/rap/
[2] https://hudson.eclipse.org/rap/job/rap-head-tools/

Comment 1 Markus Knauer

2017-06-14 07:15:12 EDT

The builds itself are failing sometime when building module A, sometimes when building module B, i.e. almost always in different modules/bundles, but the error message is always the same:


[ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-pack200b-plugin:1.0.0:pack (pack200-pack) on project org.eclipse.rap.tools.launch.rwt.test: Execution pack200-pack of goal org.eclipse.tycho.extras:tycho-pack200b-plugin:1.0.0:pack failed: MALFORMED -> [Help 1]


While there were other reports about pack200 issue on cross-projects-dev mailing list, we are using Java 8 "latest:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00)
Maven home: /shared/common/apache-maven-latest
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /opt/public/common/jdk1.8.0_121.x64/jre


While trying to "fix" this issue, we did the following actions without success:

(1) RAP Hudson
https://hudson.eclipse.org/rap/maven/
Maven Settings e23a0b6a-ab36-4ea3-8d97-c6ce7ba3db90
Remove `proxies`

  <proxies>
    <proxy>
      <id>httpproxy</id>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.eclipse.org</host>
      <port>9898</port>
      <nonProxyHosts>localhost|127.0.0.1|*.eclipse.org|172.30.206.*</nonProxyHosts>
    </proxy>
    <proxy>
      <id>httpsproxy</id>
      <active>true</active>
      <protocol>https</protocol>
      <host>proxy.eclipse.org</host>
      <port>9898</port>
      <nonProxyHosts>localhost|127.0.0.1|*.eclipse.org|172.30.206.*</nonProxyHosts>
    </proxy>
  </proxies>

(2a) RAP Hudson
https://hudson.eclipse.org/rap/configure
Environment variables
Remove all of them

ANT_ARGS
-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*|*.eclipse.org" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*|*.eclipse.org"

ANT_OPTS
-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*|*.eclipse.org" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*|*.eclipse.org"

JAVA_ARGS
-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*|*.eclipse.org" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*|*.eclipse.org"

JVM_OPTS
-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*|*.eclipse.org" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*|*.eclipse.org"


(2b) RAP Hudson
https://hudson.eclipse.org/rap/configure
Maven 2/3 Legacy Project Configuration
Remove Global MAVEN_OPTS

-Dhttp.proxyHost=proxy.eclipse.org
-Dhttp.proxyPort=9898
-Dhttps.proxyHost=proxy.eclipse.org
-Dhttps.proxyPort=9898
-Dhttp.nonProxyHosts=172.30.206.*|*.eclipse.org
-Dhttps.nonProxyHosts=172.30.206.*|*.eclipse.org


(3) RAP Tools Job Configuration
https://hudson.eclipse.org/rap/job/rap-head-tools/configure
Job - Build - Invoke Maven 3 - Properties
Remove baseline repository specification (and disable using a baseline repo which could contain malicious pack200 files)

baseline-repository=http://download.eclipse.org/rt/rap/tools/3.2/

Comment 2 Ivan Furnadjiev

2017-06-15 03:13:26 EDT

This issue was a bad "timeout" handling introduced by the jarsigner. Fixed by updating the jarsigner to the latest version.