Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 427589 - Linux tests for R4_3_maintenance run with 1.6 JRE, not 1.7
Summary: Linux tests for R4_3_maintenance run with 1.6 JRE, not 1.7
Status: RESOLVED DUPLICATE of bug 390986
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.3.1   Edit
Hardware: PC Unix All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 12:40 EST by Markus Keller CLA
Modified: 2015-08-11 12:25 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2014-02-06 12:40:20 EST
Linux tests for R4_3_maintenance run with a 1.6 JRE, not 1.7 as advertized on the test results page.

See e.g. http://download.eclipse.org/eclipse/downloads/drops4/M20140205-0800/testresults/html/org.eclipse.ant.tests.core_linux.gtk.x86_6.0.html (scroll down, click "Properties").

For 4.3.1, the test results page did say "Linux, 1.6 VM":
http://download.eclipse.org/eclipse/downloads/drops4/R-4.3.1-201309111000/testResults.php

Mac tests run with 1.7, although the links end with _macosx.cocoa.x86_5.0.html

I don't need any infrastructure changes -- I just don't like wrong information.
Comment 1 David Williams CLA 2014-03-25 21:27:36 EDT
Part of this is a dup of bug 390986 (the part about inaccurate labels), just recently rediscovered in bug 431047 and  bug 431143). 

But, the part about the VM being "incorrectly set" was a valid bug, and even though we are not doing maintenance builds any longer, I have recently discovered the source of my confusion, or mistake in setting what was intended. 

The VM can be be specified in a few places, and I must have missed one of them. 

One of settings is specifically for the VM to use to invoke ant runner. And that one will be used to "run the tests" if no other VM is set. 

But, there is another place to set VMs (usually one, but could be multiple) to run specific invoke the tests with. 

So, I'll use this bug to "improve documentation" on where and what the various VM settings are for.
Comment 2 David Williams CLA 2015-08-11 12:25:45 EDT
We "won't fix" anything for "4.3", but the general problem and solution is being tracked in bug 390986.

*** This bug has been marked as a duplicate of bug 390986 ***