[LLVMdev] Problems with nighttest FeatureTests
Brian Gaeke
gaeke at uiuc.edu
Wed Nov 3 09:28:37 PST 2004
Near as I can tell, we're looking at the following traceback:
File "/lib/qm/qm/test/target.py", line 208, in RunTest
File "/lib/qm/qm/test/database.py", line 281, in Run
File "/lib/qm/qm/test/database.py", line 188, in _Execute
File "", line 0, in ?
File "/Users/gaeke/llvm/test/QMTest/llvm.py", line 622, in Run
if (ExecProgram ((as, input, '-f', '-o', bc1))):
File "/Users/gaeke/llvm/test/QMTest/llvm.py", line 84, in
ExecProgram
(pid, status) = os.waitpid (child, 0 )
On Nov 3, 2004, at 11:26 AM, John Criswell wrote:
> Brian Gaeke wrote:
>> A typo in test/Makefile was the trigger for this problem:
>>
>> http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/
>> 020216.html
>> John, can you please look into this bug some more and add some error
>> checking to the llvm-specific qmtest python modules to make this
>> error less severe?
>
> Does the fork bomb occur in the LLVM Python code or in the QMTest
> library code that looks up the name of the configuration variable?
>
> -- John T.
>
>> Thanks!
>> -Brian
>> On Nov 3, 2004, at 10:35 AM, Brian Gaeke wrote:
>>>
>>> I think there is a very similar situation with the PowerPC/Mac OS X
>>> nightly tests. Over each of the past few nights, something has been
>>> filling up the process table, causing me to be unable to log in.
>>> The nightly tester wrote out regression test and feature test logs
>>> featuring hundreds of "Resource temporarily unavailable" errors from
>>> fork(), so I assume it's the qmtest stuff that's filling the
>>> process table. More to come once I am able to duplicate the problem
>>> and inspect the situation...
>>>
>>> -Brian
>>>
>>> On Nov 3, 2004, at 5:01 AM, Vladimir Merzliakov wrote:
>>>
>>>>>> I'm not sure that I follow. The qmtest stuff isn't working on
>>>>>> Zion
>>>>>> because (I believe) of an upgrade that happened on the machine
>>>>>> (the qmtest
>>>>>> binary doesn't work anymore?). Are you seeing a problem on
>>>>>> freebsd where
>>>>>> the feature tests go into a loop? If so, can you provide us with
>>>>>> more
>>>>>> information?
>>>>>>
>>>> make, ~ > ps -xu
>>>> USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME
>>>> COMMAND
>>>> wanderer 35325 5.0 1.7 11740 8816 ?? R 2:56AM 35:58.91
>>>> [python]
>>>> wanderer 35330 5.0 1.7 11740 8828 ?? R 2:56AM 36:16.64
>>>> [python]
>>>> wanderer 35333 5.0 1.7 11740 8828 ?? R 2:56AM 36:12.17
>>>> [python]
>>>> wanderer 35335 5.0 1.7 11740 8828 ?? R 2:56AM 36:25.80
>>>> [python]
>>>> wanderer 35337 5.0 1.7 11740 8828 ?? R 2:56AM 36:24.76
>>>> [python]
>>>> wanderer 35338 5.0 1.7 11740 8828 ?? R 2:56AM 36:21.73
>>>> [python]
>>>> wanderer 35326 4.9 1.7 11740 8828 ?? R 2:56AM 36:09.46
>>>> [python]
>>>> wanderer 35332 4.9 1.7 11740 8828 ?? R 2:56AM 36:14.49
>>>> [python]
>>>> wanderer 35339 4.9 1.7 11740 8828 ?? R 2:56AM 36:29.35
>>>> [python]
>>>> wanderer 35341 4.9 1.7 11740 8828 ?? R 2:56AM 36:26.81
>>>> [python]
>>>> wanderer 35342 4.9 1.7 11740 8828 ?? R 2:56AM 36:38.68
>>>> [python]
>>>> wanderer 35327 4.9 1.7 11740 8828 ?? R 2:56AM 36:09.99
>>>> [python]
>>>> wanderer 35328 4.9 1.7 11740 8828 ?? R 2:56AM 36:05.47
>>>> [python]
>>>> wanderer 35329 4.9 1.7 11740 8828 ?? R 2:56AM 36:08.62
>>>> [python]
>>>> wanderer 35331 4.9 1.7 11740 8828 ?? R 2:56AM 36:18.76
>>>> [python]
>>>> wanderer 35334 4.9 1.7 11740 8828 ?? R 2:56AM 36:23.59
>>>> [python]
>>>> wanderer 35336 4.9 1.7 11740 8828 ?? R 2:56AM 36:21.37
>>>> [python]
>>>> wanderer 35340 4.9 1.7 11740 8828 ?? R 2:56AM 36:22.03
>>>> [python]
>>>> wanderer 10005 0.0 0.2 1792 1004 ?? Is 2:13AM 0:00.01
>>>> /bin/sh -c cd /home/wanderer/pkg/build/llvm/night && ./testr
>>>> wanderer 10006 0.0 0.2 1800 1040 ?? I 2:13AM 0:00.01
>>>> /bin/sh - ./testrun
>>>> wanderer 10011 0.0 0.4 3020 2332 ?? I 2:13AM 0:00.06
>>>> [perl]
>>>> wanderer 35234 0.0 0.2 1796 1032 ?? I 2:55AM 0:00.00 sh
>>>> -c (time -p gmake -j2 -l3.0 -C test Feature.t) > /home/w
>>>> wanderer 35235 0.0 0.1 1308 576 ?? I 2:55AM 0:00.00
>>>> time -p gmake -j2 -l3.0 -C test Feature.t
>>>> wanderer 35236 0.0 0.2 2604 1224 ?? I 2:55AM 0:00.03
>>>> gmake -j2 -l3.0 -C test Feature.t
>>>> wanderer 35319 0.0 0.2 1796 1036 ?? I 2:56AM 0:00.00 [sh]
>>>> wanderer 35320 0.0 1.7 11740 8808 ?? I 2:56AM 0:00.57
>>>> [python]
>>>> wanderer 35343 0.0 1.7 11740 8820 ?? I 2:56AM 0:00.02
>>>> [python]
>>>> make, ~/pkg/build/gcc >
>>>>
>>>> NightlyTest.pl run with -noremove and then i can send any generated
>>>> file if need.
>>>>
>>>> Vladimir
>>>> <2004-11-03-FeatureTests-
>>>> Log.txt>_______________________________________________
>>>> LLVM Developers mailing list
>>>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>>>> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>>>
>>>
>>> _______________________________________________
>>> LLVM Developers mailing list
>>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>>> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
> --
> *********************************************************************
> * John T. Criswell Email: criswell at uiuc.edu *
> * Research Programmer *
> * University of Illinois at Urbana-Champaign *
> * *
> * "It's today!" said Piglet. "My favorite day," said Pooh. *
> *********************************************************************
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
More information about the llvm-dev
mailing list