[prev in list] [next in list] [prev in thread] [next in thread]
List: dejagnu
Subject: =?gb18030?B?u9i4tKO6IEhvdyB0byBleGVjdXRlICJydW50ZXN0?= =?gb18030?B?IiB3aXRoIG11bHQtdGhyZWFkcz8=?=
From: "=?gb18030?B?sNe6rrfj?=" <799942558 () qq ! com>
Date: 2022-09-23 3:33:57
Message-ID: tencent_0A36A938086800C217F43B9BEF4137C9A806 () qq ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
Thank you very much for your reply.
Lin
------------------ ÔʼÓʼþ ------------------
·¢¼þÈË: \
"jcb62281" \
<jcb62281@gmail.com>; ·¢ËÍʱ¼ä: 2022Äê9Ô 23ÈÕ(ÐÇÆÚÎå) ÉÏÎç10:51
ÊÕ¼þÈË: "°×º®·ã"<799942558@qq.com>;
³ËÍ: "dejagnu"<dejagnu@gnu.org>;
Ö÷Ìâ: Re: How to execute "runtest" with mult-threads?
°×º®·ã wrote:
> Hi, dejagnu
>
> I am a contributer for GCC.
>
> After I fix some bugs in GCC, I often use dejagnu to test GCC by a
> command like "make check-gcc ..." and use "-j" to speed up.
>
> I want to verify a distributed version of GCC in openEuler, recently.
> I think I only use "runtest --srcdir /path/testsuite -tool gcc ..." to
> test GCC, because it only has a binary version. But I didn't see any
> args like "-j" to speed up "runtest". Do I ignore some important tips?
> So do you have some tips that can help me to speed up the test with
> distributed version GCC?
>
> Any suggestions would be appreciated.
The best way to do this at the moment is to run subsets of the testsuite
separately in parallel runtest processes. The smallest unit that can be
parceled out in this way is each individual *.exp test script. The most
convenient unit is each tool, but that will not help with testing GCC.
Native parallel testing support is a long-term goal for DejaGnu, but
will require extensive infrastructure improvements and some cooperation
from testsuites.
Parallel testing is also completely impossible for some targets, such as
the embedded boards that were a major historical impetus for DejaGnu.
Again, eventual infrastructure improvements may allow for parallel
testing if multiple boards are available, but, historically, using
multiple boards was economically infeasible.
-- Jacob
[Attachment #3 (text/html)]
<meta http-equiv="Content-Type" content="text/html; charset=GB18030"><div>Thank you \
very much for your reply.</div><div><br></div><div>Lin</div><div><hr align="left" \
style="margin: 0 0 10px 0;border: 0;border-bottom:1px solid \
#E4E5E6;height:0;line-height:0;font-size:0;padding: 20px 0 0 0;width: 50px;"><div \
style="font-size:14px;font-family:Verdana;color:#000;"><div> </div></div></div><div> </div><div \
style="position: relative;"><div><br></div><div><br></div><div style="font-size: \
12px;font-family: Arial Narrow;padding:2px 0 2px \
0;">------------------ ÔʼÓʼþ ------------------</div><div \
style="font-size: 12px;background:#efefef;padding:8px;"><div><b>·¢¼þÈË:</b> \
"jcb62281" \
<jcb62281@gmail.com>;</div><div><b>·¢ËÍʱ¼ä:</b> 2022Äê9Ô 23ÈÕ(ÐÇÆÚÎå) \
ÉÏÎç10:51</div><div><b>ÊÕ¼þÈË:</b> "°×º®·ã"<799942558@qq.com>;<wbr></div><d \
iv><b>³ËÍ:</b> "dejagnu"<dejagnu@gnu.org>;<wbr></div><div><b>Ö÷Ìâ:</b> Re: \
How to execute "runtest" with mult-threads?</div></div><div><br></div>°×º®·ã \
wrote:<br>> Hi, dejagnu<br>><br>> I am a contributer for GCC. \
<br>><br>> After I fix some bugs in GCC, I often use dejagnu to test GCC by a \
<br>> command like "make check-gcc ..." and use "-j" to speed up.<br>><br>> \
I want to verify a distributed version of GCC in openEuler, recently. <br>> I \
think I only use "runtest --srcdir /path/testsuite -tool gcc ..." to <br>> test \
GCC, because it only has a binary version. But I didn't see any <br>> args like \
"-j" to speed up "runtest". Do I ignore some important tips? <br>> So do you have \
some tips that can help me to speed up the test with <br>> distributed version \
GCC?<br>><br>> Any suggestions would be appreciated.<br><br>The best way to do \
this at the moment is to run subsets of the testsuite <br>separately in parallel \
runtest processes. The smallest unit that can be <br>parceled out in this way \
is each individual *.exp test script. The most <br>convenient unit is each \
tool, but that will not help with testing GCC.<br><br>Native parallel testing support \
is a long-term goal for DejaGnu, but <br>will require extensive infrastructure \
improvements and some cooperation <br>from testsuites.<br><br>Parallel testing is \
also completely impossible for some targets, such as <br>the embedded boards that \
were a major historical impetus for DejaGnu. <br>Again, eventual infrastructure \
improvements may allow for parallel <br>testing if multiple boards are available, \
but, historically, using <br>multiple boards was economically \
infeasible.<br><br><br>-- Jacob<br></div>
jcb6a
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic