Closed
Bug 409221
Opened 18 years ago
Closed 18 years ago
JSS test tries to use amd64 Java on sparcv9 for 64bit test
Categories
(JSS Graveyard :: Tests, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
4.2.6
People
(Reporter: christophe.ravel.bugs, Assigned: christophe.ravel.bugs)
Details
Attachments
(1 file)
|
642 bytes,
patch
|
glenbeasley
:
review+
|
Details | Diff | Splinter Review |
Thu Dec 20 08:36:31 PST 2007: Start JSS tests for SunOS5.10_64_DBG
================
DEBUG in SunOS
DEBUG java=/share/builds/components/jdk/1.5.0_09/SunOS64/jre/bin/java
DEBUG cpu=sparcv9
DEBUG java=/share/builds/components/jdk/1.5.0_09/SunOS64/jre/bin/amd64/java
'/share/builds/components/jdk/1.5.0_09/SunOS64/jre/bin/amd64/java' does not exist
Thu Dec 20 08:36:31 PST 2007: End JSS tests for SunOS5.10_64_DBG
| Assignee | ||
Comment 1•18 years ago
|
||
There are 2 issues with the following code:
#
# Use 64-bit Java on AMD64.
#
my $java_64bit = 0;
if ($osname eq "SunOS") {
if ($ENV{USE_64}) {
my $cpu = `/usr/bin/isainfo -n`;
if ($cpu == "amd64") {
$java = "$ENV{JAVA_HOME}/jre/bin/amd64/java$exe_suffix";
$java_64bit = 1;
}
}
}
Issue #1: $cpu needs to be chomp'd after `/usr/bin/isainfo -n`
issue #2: the comparison operator for strings is "eq", not "=="
I am wondering why this ever worked before today...
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•18 years ago
|
||
Attachment #294047 -
Flags: review?(glen.beasley)
| Assignee | ||
Updated•18 years ago
|
Assignee: glen.beasley → christophe.ravel.bugs
Status: ASSIGNED → NEW
| Assignee | ||
Comment 3•18 years ago
|
||
Patch tested on Solaris SPARC and Solaris x86
Status: NEW → ASSIGNED
Updated•18 years ago
|
Attachment #294047 -
Flags: review?(glen.beasley) → review+
| Assignee | ||
Comment 4•18 years ago
|
||
Committed on the trunk:
Checking in all.pl;
/cvsroot/mozilla/security/jss/org/mozilla/jss/tests/all.pl,v <-- all.pl
new revision: 1.50; previous revision: 1.49
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Priority: -- → P2
Resolution: --- → FIXED
Target Milestone: --- → 4.2.6
You need to log in
before you can comment on or make changes to this bug.
Description
•