[M3devel] CM3 release build regression tests not terminating
Olaf Wagner
wagner at elegosoft.com
Wed Apr 29 08:20:06 CEST 2009
Quoting Tony Hosking <hosking at cs.purdue.edu>:
> Whatever changed in the last 24 hours has my tinderbox runs completing now.
Hm. The process doesn't hang anymore; I get the following errors though:
(1)
=== package m3-libs/unittest-numeric ===
+++ /home/wagner/tmp/cm3/luthien/cm3/bin/cm3 -build -override
-DROOT='/u/cm3/cm
3-ws/luthien-2009-04-29-01-30-32/cm3' +++
--- building in FreeBSD4 ---
unable to read ../src/m3overrides, options "-override" and "-x" ignored.
"/u/cm3/cm3-ws/luthien-2009-04-29-01-30-32/cm3/m3-libs/unittest-numeric/src/m3ma
kefile", line 1: quake runtime error: unable to open
"/home/wagner/tmp/cm3/luthi
en/cm3/pkg/libm3/FreeBSD4/.M3EXPORTS" for reading
--procedure-- -line- -file---
import -- <builtin>
include_dir 1
/u/cm3/cm3-ws/luthien-2009-04-29-01-30-32/cm3/m3-libs/uni
ttest-numeric/src/m3makefile
5
/u/cm3/cm3-ws/luthien-2009-04-29-01-30-32/cm3/m3-libs/uni
ttest-numeric/FreeBSD4/m3make.args
Fatal Error: package build failed
==> m3-libs/unittest-numeric done
(2)
=== package m3-sys/cm3ide ===
+++ /home/wagner/tmp/cm3/luthien/cm3/bin/cm3 -build -override
-DROOT='/u/cm3/cm
3-ws/luthien-2009-04-29-01-30-32/cm3' +++
--- building in FreeBSD4 ---
"/u/cm3/cm3-ws/luthien-2009-04-29-01-30-32/cm3/m3-sys/cm3ide/src/m3makefile",
li
ne 9: quake runtime error: unable to open
"/u/cm3/cm3-ws/luthien-2009-04-29-01-3
0-32/cm3/m3-libs/tcp/FreeBSD4/.M3EXPORTS" for reading
--procedure-- -line- -file---
import -- <builtin>
include_dir 9
/u/cm3/cm3-ws/luthien-2009-04-29-01-30-32/cm3/m3-sys/cm3i
de/src/m3makefile
6
/u/cm3/cm3-ws/luthien-2009-04-29-01-30-32/cm3/m3-sys/cm3i
de/FreeBSD4/m3make.args
Fatal Error: package build failed
==> m3-sys/cm3ide done
(3)
=== package m3-comm/stubgen ===
+++ /home/wagner/tmp/cm3/luthien/cm3/bin/cm3 -build -override
-DROOT='/u/cm3/cm
3-ws/luthien-2009-04-29-01-30-32/cm3' +++
--- building in FreeBSD4 ---
new source -> compiling Value.i3
new source -> compiling Type.i3
new source -> compiling ValueProc.i3
new source -> compiling Protocol.i3
new source -> compiling TypeNames.i3
new source -> compiling TypeNames.m3
new source -> compiling StubUtils.i3
new source -> compiling Type.m3
"../src/Type.m3", line 291: types are not assignable
1 error encountered
new source -> compiling Value.m3
new source -> compiling AstToType.i3
new source -> compiling AstToVal.i3
new source -> compiling AstToVal.m3
new source -> compiling StubCode.i3
new source -> compiling FRefRefTbl.i3
new source -> compiling AstToType.m3
new source -> compiling ModuleStubCode.i3
new source -> compiling IntfStubCode.i3
new source -> compiling CodeForType.i3
new source -> compiling StubCode.m3
new source -> compiling CodeForType.m3
new source -> compiling ModuleStubCode.m3
new source -> compiling IntfStubCode.m3
new source -> compiling StubGenTool.i3
new source -> compiling StubGenTool.m3
new source -> compiling StubUtils.m3
new source -> compiling FRefRefTbl.m3
new source -> compiling Main.m3
new exporters -> recompiling ValueProc.i3
new exporters -> recompiling Type.i3
new opaque info -> recompiling TypeNames.m3
new opaque info -> recompiling AstToVal.m3
new opaque info -> recompiling AstToType.m3
new opaque info -> recompiling StubGenTool.m3
compilation failed => not building program "stubgen"
Fatal Error: package build failed
*** execution of /home/wagner/tmp/cm3/luthien/cm3/bin/cm3 -build
-override -DROOT='/u/cm3/cm3-ws/luthien-2009-04-29-01-30-32/cm3'
failed ***
real 82m36.775s
user 25m38.739s
sys 14m12.884s
Tinderbox currently does not show any success, too.
It seems that still more is amiss.
Olaf
>
> On 28 Apr 2009, at 22:13, Jay wrote:
>
>>
>> Tony can you clarify? Things stopped working two weeks ago?
>> Or things were working until more recently?
>>
>>
>>
>> It seems like the select call never returns.
>> Whatever is going on, it troubles debugging tools.
>> gdb won't follow the children..which is probably ok, they aren't
>> the problem.
>> truss can't be control-c'ed, but can be killed.
>> "info locals" in gdb often hangs and I have to pkill gdb.
>> Not that info locals ever works well, but it usually doesn't hang gdb.
>> I started putting in RTIO calls.
>> WaitForAll's finishes one Wait call but then hangs on the next.
>>
>>
>> I think we should not run cminstall against 5.4 runtime.
>> Enable user threads as some related scenario..
>>
>>
>> - Jay
>>
>>
>> ________________________________
>>> CC: m3devel at elegosoft.com; manderson at elegosoft.com
>>> From: hosking at cs.purdue.edu
>>> To: jay.krell at cornell.edu
>>> Subject: Re: [M3devel] CM3 release build regression tests not terminating
>>> Date: Tue, 28 Apr 2009 21:49:32 +1000
>>>
>>> Sounds about right.
>>>
>>> Antony Hosking | Associate Professor | Computer Science | Purdue University
>>> 305 N. University Street | West Lafayette | IN 47907 | USA
>>> Office +1 765 494 6001 | Mobile +1 765 427 5484
>>>
>>>
>>>
>>> On 28 Apr 2009, at 21:17, Jay wrote:
>>>
>>>
>>> The changes went in two weeks ago 4/14, were they definitely working?
>>> I can try it again, hopefully without the full tinderbox stuff.
>>>
>>> - Jay
>>>
>>>
>>> ----------------------------------------
>>> From: hosking at cs.purdue.edu
>>> To: jay.krell at cornell.edu
>>> Date: Tue, 28 Apr 2009 21:11:42 +1000
>>> CC: m3devel at elegosoft.com; manderson at elegosoft.com
>>> Subject: Re: [M3devel] CM3 release build regression tests not terminating
>>>
>>> What could possibly have changed here. It used to work fine on
>>> multiple platforms.
>>>
>>> On 28 Apr 2009, at 20:14, Jay wrote:
>>>
>>>
>>> It creates a file named "df-k" and hangs here:
>>>
>>> (gdb) where
>>> #0 0x080f417f in select ()
>>> #1 0x080e0567 in m3_select (nfds=0, readfds=0x28127128,
>>> writefds=0x28127138,
>>> exceptfds=0x28127148, timeout=0xbfbfe6d8) at ../src/runtime/
>>> FreeBSD4/select.c:13
>>> #2 0x080c840e in ThreadPosix__CallSelect (M3_Cwb5VA_nfd=0,
>>> M3_CEtG8K_timeout=0xbfbfe6d8)
>>> at ThreadPosix.m3:714
>>> #3 0x080c993b in ThreadPosix__InternalYield () at ThreadPosix.m3:985
>>> #4 0x080c755f in ThreadPosix__XPause (M3_DZQH1o_until=0xbfbfe770,
>>> M3_AicXUJ_alertable=0 '\0')
>>> at ThreadPosix.m3:555
>>> #5 0x080c746b in Thread__Pause (M3_CtKayy_n=0.10000000000000001) at
>>> ThreadPosix.m3:539
>>> #6 0x0808c8d4 in Process__Wait (M3_AUwVTW_p=0x2813ae94) at
>>> ProcessPosix.m3:294
>>> #7 0x08080b31 in System__ExecuteList__WaitForAll.1 () at
>>> System.m3:527
>>> #8 0x08082013 in System__ExecuteList (M3_Bd56fi_cmd=0x2813a564,
>>> M3_EkfbeH_env=0x0,
>>> M3_DLmMvC_msgif=0x0, M3_Bd56fi_wd=0x0) at System.m3:737
>>> #9 0x0804bc1e in OS__GetDiskSpace (M3_Bd56fi_dir=0x28136f14) at
>>> OSPOSIX.m3:19
>>> #10 0x0804c31c in Main__DoIt () at Main.m3:122
>>> #11 0x0805107c in Main_M3 (M3_AcxOUs_mode=1) at Main.m3:1078
>>> #12 0x080bb77e in RTLinker__RunMainBody (M3_DjPxE3_m=0x81270a0) at
>>> RTLinker.m3:395
>>> #13 0x080bad24 in RTLinker__AddUnitI (M3_DjPxE3_m=0x81270a0) at
>>> RTLinker.m3:109
>>> #14 0x080badaa in RTLinker__AddUnit (M3_DjPxE5_b=0x8051031) at
>>> RTLinker.m3:118
>>> #15 0x08048220 in main (argc=4, argv=0xbfbfec78, envp=0xbfbfec8c) at
>>> _m3main.mc:4
>>>
>>> Notice it using user threads, so old m3core/libm3.
>>> df doesn't appear to be any longer running.
>>> Why it prints about the backend mode, I don't know.
>>>
>>> (and yes, I get it -- df -k is directly related to GetDiskSpace..if
>>> this is how one checks diskspace on Unix...I think we should punt,
>>> unless posix actually specifies the precise output format of this
>>> command it is very reliably parsed...)
>>>
>>> - Jay
>>>
>>>
>>> ----------------------------------------
>>> From: jay.krell at cornell.edu
>>> To: wagner at elegosoft.com
>>> CC: hosking at cs.purdue.edu; m3devel at elegosoft.com; manderson at elegosoft.com
>>> Subject: RE: [M3devel] CM3 release build regression tests not
>>> terminating
>>> Date: Tue, 28 Apr 2009 09:58:56 +0000
>>>
>>>
>>> Right, now it hangs having printed..I know this looks a bit of
>>> nonsense..stuff from right around:
>>>
>>>
>>> M3_BACKEND_MODE = "3"
>>> % -- defines how the frontend, backend, and assembler interact
>>> % "0" -- don't call m3_backend, M3CG produces object code
>>> % "1" -- don't call m3_backend, M3CG produces assembly code
>>> % "2" -- call m3_backend, it produces object code
>>> % "3" -- call m3_backend, it produces assembly code
>>>
>>>
>>> however, this is noticably pretty close to the last BEGIN_CONFIG.
>>>
>>> Maybe the carriage returns confused it. I'll see..
>>> I did introduce them recently by accident.
>>> gdb reported some errors and no symbols in the callstack having
>>> connected to it, on FreeBSD. If need be I can try debugging it on
>>> another system..
>>>
>>>
>>> (aside, philosophy: all text processing code should treat \n, \r,
>>> and \r\n in put the same, unless you are writing a terminal driver,
>>> then \r has a separate meaning useful for implementing spinners..)
>>>
>>>
>>> - Jay
>>>
>>>
>>> ----------------------------------------
>>> Date: Tue, 28 Apr 2009 11:40:00 +0200
>>> From: wagner at elegosoft.com
>>> To: jay.krell at cornell.edu
>>> CC: hosking at cs.purdue.edu; m3devel at elegosoft.com; manderson at elegosoft.com
>>> Subject: RE: [M3devel] CM3 release build regression tests not
>>> terminating
>>>
>>> Quoting Jay :
>>>
>>>
>>> Well, on FreeBSD 7.0, I get as far as:
>>>
>>> ew source -> compiling EnvUtils.i3
>>> libexec/ld-elf.so.1: Shared object "libc.so.6" not found,
>>> required by "cm3cg"
>>> ew source -> compiling EnvUtils.m3
>>> libexec/ld-elf.so.1: Shared object "libc.so.6" not found,
>>> required by "cm3cg"
>>> ew source -> compiling FingerprintFmt.i3
>>> libexec/ld-elf.so.1: Shared object "libc.so.6" not found,
>>> required by "cm3cg"
>>> ew source -> compiling TextUtils.i3
>>> libexec/ld-elf.so.1: Shared object "libc.so.6" not found,
>>> required by "cm3cg"
>>>
>>> Yeah, I understand, I have libc.so.7.
>>>
>>> You need to install the FreeBSD compat packages for backward
>>> compatibility. Should work fine then (until cminstall hangs?).
>>>
>>> Olaf
>>>
>>>
>>> - Jay
>>>
>>>
>>> ----------------------------------------
>>> From: jay.krell at cornell.edu
>>> To: hosking at cs.purdue.edu; wagner at elegosoft.com
>>> Date: Tue, 28 Apr 2009 07:45:14 +0000
>>> CC: m3devel at elegosoft.com; manderson at elegosoft.com
>>> Subject: Re: [M3devel] CM3 release build regression tests not
>>> terminating
>>>
>>>
>>> I've never been able to get the tinderbox stuff to work for me.
>>> I'll try again.
>>> Nothing much from me lately -- pthreads movement to C, and then
>>> back.
>>>
>>> Jay, did you change any config files recently?
>>>
>>> FreeBSD config file changes on 2009-04-13.
>>>
>>> - Jay
>>>
>>> ----------------------------------------
>>> From: hosking at cs.purdue.edu
>>> To: wagner at elegosoft.com
>>> Date: Tue, 28 Apr 2009 16:45:29 +1000
>>> CC: m3devel at elegosoft.com; manderson at elegosoft.com
>>> Subject: Re: [M3devel] CM3 release build regression tests not
>>> terminating
>>>
>>> Yes, I had noticed this too.
>>>
>>> On 28 Apr 2009, at 16:29, Olaf Wagner wrote:
>>>
>>> Hi,
>>>
>>> does anybody know what's keeping the release-build tests for
>>> tinderbox
>>> from terminating? I've got lots of stalled regression process
>>> trees on
>>> my system, and the tinderbox display indicates that none of the
>>> release
>>> builds seem to succeed. Has anybody changed anything in the
>>> scripts?
>>>
>>> On a closer look, upgrade seems to be stuck in the installer:
>>>
>>> % ps -axwww 25310
>>> PID TT STAT TIME COMMAND
>>> 25310 ?? S 2:15.61 /home/wagner/work/cm3-inst/luthien/current/
>>> pkg/cminstall/FreeBSD4/cminstall -c /home/wagner/work/cm3-inst/
>>> luthien/current -o
>>>
>>> Jay, did you change any config files recently?
>>> Regression tests seemed to have been running again for some
>>> days,
>>> and then
>>> stopped again.
>>>
>>> I'll try to investigate further this evening, but must leave
>>> now for
>>> other work...
>>>
>>> Olaf
>>> --
>>> Olaf Wagner -- elego Software Solutions GmbH
>>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin,
>>> Germany
>>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30
>>> 23
>>> 45 86 95
>>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz:
>>> Berlin
>>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:
>>> DE163214194
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Olaf Wagner -- elego Software Solutions GmbH
>>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23
>>> 45 86 95
>>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz:
>>> Berlin
>>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:
>>> DE163214194
>>>
>>>
>>>
--
Olaf Wagner -- elego Software Solutions GmbH
Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
More information about the M3devel
mailing list