Your message dated Fri, 7 Oct 2016 10:30:59 +0200
with message-id <[email protected]>
and subject line Re: Bug#828931: llvm-toolchain-3.7: FTBFS on i386 with gcc-6
and glibc 2.23
has caused the Debian Bug report #828931,
regarding llvm-toolchain-3.7: FTBFS on i386 with gcc-6 and glibc 2.23
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
828931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828931
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: llvm-toolchain-3.7
Version: 1:3.7.1-2
Severity: important
>From my pbuilder build log, using a chroot preferring gcc-defaults and
glibc from experimental:
...
======================================================================
ERROR: test_lldbmi_tokens (TestMiSyntax.MiSyntaxTestCase)
Test that 'lldb-mi --interpreter' prints command tokens.
----------------------------------------------------------------------
Traceback (most recent call last):
File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/lldbtest.py", line
483, in wrapper
return func(self, *args, **kwargs)
File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/lldbtest.py", line
598, in wrapper
func(*args, **kwargs)
File
"/build/llvm-toolchain-3.7-3.7.1/lldb/test/tools/lldb-mi/syntax/TestMiSyntax.py",
line 30, in test_lldbmi_tokens
self.expect("\*stopped,reason=\"breakpoint-hit\"")
File
"/build/llvm-toolchain-3.7-3.7.1/lldb/test/tools/lldb-mi/lldbmi_testcase.py",
line 48, in expect
return self.child.expect(pattern, *args, **kwargs)
File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/pexpect-2.4/pexpect.py",
line 1316, in expect
return self.expect_list(compiled_pattern_list, timeout, searchwindowsize)
File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/pexpect-2.4/pexpect.py",
line 1330, in expect_list
return self.expect_loop(searcher_re(pattern_list), timeout,
searchwindowsize)
File "/build/llvm-toolchain-3.7-3.7.1/lldb/test/pexpect-2.4/pexpect.py",
line 1414, in expect_loop
raise TIMEOUT (str(e) + '\n' + str(self))
TIMEOUT: Timeout exceeded in read_nonblocking().
<pexpect.spawn object at 0xf212178c>
version: 2.4 ($Revision: 516 $)
command: /build/llvm-toolchain-3.7-3.7.1/build-llvm/Release/bin/lldb-mi
args: ['/build/llvm-toolchain-3.7-3.7.1/build-llvm/Release/bin/lldb-mi',
'--interpreter']
searcher: searcher_re:
0: re.compile("\*stopped,reason="breakpoint-hit"")
buffer (last 100 chars): mi/syntax/a.out",symbols-loaded="0",loaded_addr="-"
(gdb)
*running,thread-id="all"
(gdb)
(gdb)
before (last 100 chars): mi/syntax/a.out",symbols-loaded="0",loaded_addr="-"
(gdb)
*running,thread-id="all"
(gdb)
(gdb)
after: <class 'pexpect.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 29937
child_fd: 4
closed: False
timeout: 30
delimiter: <class 'pexpect.EOF'>
logfile: None
logfile_read: <open file 'child.log', mode 'w' at 0xf21972e0>
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
Config=i686-gcc-6
----------------------------------------------------------------------
RESULT: FAILED (0 passes, 0 failures, 2 errors, 0 skipped, 1 expected
failures, 0 unexpected successes)
381 out of 388 test suites processed
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
Hi,
> As I am expecting to remove llvm toolchain 3.7 soon, I won't work on it.
> Please try with 3.8 or 3.9 instead.
that new glibc and gcc are now part of unstable, and the package rebuilds
cleanly.
closing this bug since it isn't reproducible.
G.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
