Your message dated Sat, 5 Jan 2002 03:10:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#127783: gcc-3.0-source: java selftest fail
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Jan 2002 15:13:34 +0000
>From [EMAIL PROTECTED] Fri Jan 04 09:13:34 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mailout05.sul.t-online.com [194.25.134.82] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 16MW2H-0001lg-00; Fri, 04 Jan 2002 09:13:33 -0600
Received: from fwd04.sul.t-online.de 
        by mailout05.sul.t-online.de with smtp 
        id 16MW2G-0000XG-0E; Fri, 04 Jan 2002 16:13:32 +0100
Received: from dual ([EMAIL PROTECTED]) by fmrl04.sul.t-online.com
        with esmtp id 16MW2D-1uesT2C; Fri, 4 Jan 2002 16:13:29 +0100
Received: from mrvn by dual with local (Exim 3.33 #1 (Debian))
        id 16MW2C-0003cM-00; Fri, 04 Jan 2002 16:13:28 +0100
From: Goswin Brederlow <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc-3.0-source: java selftest fail
X-Reportbug-Version: 1.41.14213
X-Mailer: reportbug 1.41.14213
Date: Fri, 04 Jan 2002 16:13:28 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: Goswin Brederlow <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]

Package: gcc-3.0
Version: 1:3.0.3-1
Severity: normal

The package doesn't pass its selftests and _should_fail_ to build.
It should fail when the first make fails and not continue with other
selftest, otherwise errors get overlocked.

The timeout might be the reason why it fails to build on m68k,
something just takes too long during build.

MfG
        Goswin

======================================================================
WARNING: Couldn't find the global config file.
Test Run By mrvn on Fri Jan  4 15:47:05 2002
Native configuration is i386-pc-linux-gnu

                === libjava tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /tmp/gcc-3.0-3.0.3ds3/src/libjava/testsuite/config/default.exp as 
tool-and-target-specific interface file.
Running /tmp/gcc-3.0-3.0.3ds3/src/libjava/testsuite/libjava.compile/compile.exp 
...
Running /tmp/gcc-3.0-3.0.3ds3/src/libjava/testsuite/libjava.lang/lang.exp ...
XPASS: stub compilation from source
XPASS: stub byte compilation
XPASS: stub compilation from bytecode
XPASS: stub -O compilation from source
XPASS: stub byte compilation
XPASS: stub -O compilation from bytecode
expected was zardoz
output was q=0
zardoz
XPASS: stringconst output from bytecode->native test
expected was zardoz
output was q=0
zardoz
XPASS: stringconst -O output from bytecode->native test
WARNING: program timed out.
FAIL: direct_write -O execution from bytecode->native test
XPASS: N19990310_4 output from source compiled test
expected was OK
output was NG
XPASS: N19990310_4 -O output from source compiled test
expected was OK
output was NG
Running /tmp/gcc-3.0-3.0.3ds3/src/libjava/testsuite/libjava.mauve/mauve.exp ...

                === libjava Summary ===

# of expected passes            1674
# of unexpected failures        1
# of unexpected successes       10
# of expected failures          14
# of untested testcases         17
make[5]: *** [check-DEJAGNU] Error 1
make[5]: Leaving directory 
`/tmp/gcc-3.0-3.0.3ds3/build/i386-linux/libjava/testsuite'
make[4]: *** [check-am] Error 2
make[4]: Target `check' not remade because of errors.
make[4]: Leaving directory 
`/tmp/gcc-3.0-3.0.3ds3/build/i386-linux/libjava/testsuite'
======================================================================

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux dual 2.4.16 #2 SMP Sun Dec 2 15:35:42 CET 2001 i686
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages gcc-3.0 depends on:
ii  binutils                2.11.92.0.12.3-4 The GNU assembler, linker and bina
ii  cpp-3.0                 1:3.0.3-1        The GNU C preprocessor.
ii  gcc-3.0-base            1:3.0.3-1        The GNU Compiler Collection (base 
ii  libc6                   2.2.4-7          GNU C Library: Shared libraries an
ii  libgcc1                 1:3.0.3-1        GCC support library.


---------------------------------------
Received: (at 127783-done) by bugs.debian.org; 5 Jan 2002 02:13:25 +0000
>From [EMAIL PROTECTED] Fri Jan 04 20:13:25 2002
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 16MgKq-0002aW-00; Fri, 04 Jan 2002 20:13:24 -0600
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
        by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id DAA05290;
        Sat, 5 Jan 2002 03:10:21 +0100 (MET)
Received: (from [EMAIL PROTECTED])
        by bolero.cs.tu-berlin.de (8.10.2+Sun/8.9.3) id g052ALe25556;
        Sat, 5 Jan 2002 03:10:21 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 5 Jan 2002 03:10:20 +0100
To: Goswin Brederlow <[EMAIL PROTECTED]>,
        [EMAIL PROTECTED]
CC: Roman Zippel <[EMAIL PROTECTED]>
Subject: Re: Bug#127783: gcc-3.0-source: java selftest fail
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]

Goswin Brederlow writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
> 
> > Goswin Brederlow writes:
> > > Package: gcc-3.0
> > > Version: 1:3.0.3-1
> > > Severity: normal
> > > 
> > > The package doesn't pass its selftests and _should_fail_ to build.
> > > It should fail when the first make fails and not continue with other
> > > selftest, otherwise errors get overlocked.
> > 
> > huh? then we'll never have a build which succeeds ...
> 
> Some test are expected to fail, thats fine. I hope the expected
> failures don't make the make return with an error too.
> 
> But an unexpected failure suggests a new error. That should fail and
> stop the build.

fine, if you want this behaviour on m68k, I'll do it. What do we gain?
Roman Zippel submitted the patches to build gcj on m68k, so you may
want to ask him for the failures.

> > you deleted the interesting part. where/why doesn't it continue?
> 
> It does. I think the next one was the gcc tests. That shouldn't be
> caried out since the libjava tests failed (unexpectedly).

so all is ok. regressions on architecutures, which aren't "supported"
upstream in 3.0 (Debian has it's own patches for m68k, hppa and
sparc64) are fairly common. Sure, we can just disbale running the
testsuite.


Reply via email to