Perf build failed due to missing test package from perffarm
23:30:28 getBenchmarkPackage:
23:30:28 [echo] /home/jenkins/workspace/openjdk8_hs_perftest_x86-64_linux/../benchmarks/ilog_wodm881_Package.zip
23:30:28 [echo] wget -q --http-user=${env.PERF_USERNAME} --http-password=XXX --no-check-certificate http://perffarm.hursley.ibm.com/packages/ilog_wodm881_Package.zip
perffarm.hursley.ibm.com is an internal server. Test material should be pre-staged on the machine.
Disable the builds until this is fixed: https://ci.adoptopenjdk.net/view/Perf%20tests/
Could we have some machine labeled for perf testing (i.e. ci.role.perf), so I do not need to stage perf test material on all test machine? @ShelleyLambert
Yes I can label some for perf, do you have a preference for which machines?
Can we label two linux machines for now? Thanks
https://ci.adoptopenjdk.net/computer/test-packet-ubuntu1604-x64-2/
https://ci.adoptopenjdk.net/computer/test-softlayer-ubuntu1604-x64-1/
Those 2 machines now labeled with ci.role.perf
Test material is staged on both machines under /home/jenkins/workspace/benchmarks
Test cannot run properly due to missing numactl
https://ci.adoptopenjdk.net/view/Perf%20tests/job/openjdk8_j9_perftest_x86-64_linux/108/console
21:07:14 numactl --physcpubind=0,1,36,37 --membind=0 /home/jenkins/workspace/openjdk8_j9_perftest_x86-64_linux/openjdkbinary/j2sdk-image/jre/bin/../bin/java -cp lib/asm-3.1.jar:lib/asm-analysis-3.1.jar:lib/asm-commons-3.1.jar:lib/asm-tree-3.1.jar:lib/asm-util-3.1.jar:lib/dom4j-1.6.1.jar:lib/j2ee_connector-1_5-fr.jar:lib/jrules-engine.jar:lib/jrules-res-execution.jar:lib/log4j-1.2.8.jar:lib/openxml4j-beta.jar:lib/sam.jar:lib/sizing-xom.jar:bin:bin/ra.xml -Xgcpolicy:optthruput -Xdump:system:defaults:file={perffarm_dump}/core.%Y%m%d.%H%M%S.%pid.%seq.dmp -Xdump:nofailover -Xcompressedrefs -Xverbosegclog:verbosegc.280618-190714.log -Xms1024m -Xmx1024m com.ibm.rules.bench.segmentation.RuleEngineRunner ruleset=F_JAVAXOM_Segmentation5_DE javaXOM sizeparam=1 warmup=240 timeout=400 stateful 100000000 reportPath=j2se-perf-report-87.csv jrulesVersion=8.7 DT_or_Rules=DT multithread=4 >> /home/jenkins/workspace/openjdk8_j9_perftest_x86-64_linux/jvmtest/performance/odm/ilog_wodm881/ILOG_STDOUT.txt 2>>/home/jenkins/workspace/openjdk8_j9_perftest_x86-64_linux/jvmtest/performance/odm/ilog_wodm881/ILOG_STDERR.txt
21:07:14
21:07:14 Working directory is = /home/jenkins/workspace/openjdk8_j9_perftest_x86-64_linux/jvmtest/performance/odm/ilog_wodm881
21:07:14 rulesetUsageMonitorEnabled set to false
21:07:14 Running configure.sh
21:07:14 Configuring ILOG for machine test-softlayer-ubuntu1604-x64-1
21:07:14 Using default configuration
21:07:14 * pool.maxSize = maximum number of connections in the pool, the default value is 10
21:07:14 <config-property-value>pool.maxSize=50,pool.waitTimeout=3000</config-property-value>
21:07:14 Checking value of rulesetUsageMonitorEnabled property in ra.xml
21:07:14 <config-property-name>rulesetUsageMonitorEnabled</config-property-name>
21:07:14 <config-property-type>java.lang.Boolean</config-property-type>
21:07:14 <config-property-value>true</config-property-value>
21:07:14 </config-property>
21:07:14 No Residual Trace/Logs found
21:07:14 No Residual Dumps found
21:07:14
21:07:14 =======================
21:07:14 = Running ILOG_WODM =
21:07:14 =======================
21:07:14 Error: verbosegc.280618-190714.log does not exist
21:07:14 Error: Headless GCMV cannot operate without a verbosegclog
21:07:14 *** Error: No New Trace/Logs found
21:07:14 *** No New Dumps found
jenkins@test-packet-ubuntu1604-x64-2:~$ numactl
-bash: numactl: command not found
jenkins@test-softlayer-ubuntu1604-x64-1:~$ numactl
The program 'numactl' is currently not installed. To run 'numactl' please ask your administrator to install the package 'numactl'
I do not have the rights to install numactl. @gdams Could you help us to install numactl on the following two machines? Thanks.
https://ci.adoptopenjdk.net/computer/test-packet-ubuntu1604-x64-2/
https://ci.adoptopenjdk.net/computer/test-softlayer-ubuntu1604-x64-1/
You can raise an openjdk-infrastructure issue for that request.
This issue is not valid anymore.