Displaying 6 results from an estimated 6 matches for "termnation".
Did you mean:
termination
2004 Jun 24
5
[LLVMdev] Using -noexternals option of NightlyTest.pl
> Are you using the NightlyTest.pl file? To run the tester I don't use
> gmake directly at all. Instead, I have this in my crontab:
>
> 5 3 * * *
LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs
$HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan
/home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86
>
> When run like this,
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
Vladimir,
Did the checkout fail? Its trying to do a chdir("llvm") in the build
directory (second argument to the script) but that directory doesn't
exist or isn't executable.
Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm
dir?
Reid.
On Thu, 2004-06-24 at 10:42, Vladimir Merzliakov wrote:
> > Are you using the NightlyTest.pl file? To run the
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Thu, 24 Jun 2004, Vladimir Merzliakov wrote:
> > Are you using the NightlyTest.pl file? To run the tester I don't use
> > gmake directly at all. Instead, I have this in my crontab:
> >
> > 5 3 * * *
> LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs
> $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan
>
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Thu, 24 Jun 2004, Vladimir Merzliakov wrote:
> At this moment I use
> "gmake TEST=nightly" command line to run night tester
>
> What I must specific and where to disable SPEC run (i don't have it)
I think that it's currently a bug that this does not automatically happen.
> I known about new NightlyTest.pl option: -noexternals
> But what I must do for
2004 Jun 24
3
[LLVMdev] Using -noexternals option of NightlyTest.pl
At this moment I use
"gmake TEST=nightly" command line to run night tester
What I must specific and where to disable SPEC run (i don't have it)
I known about new NightlyTest.pl option: -noexternals
But what I must do for enable it
Vladimir
2010 Aug 02
5
mapping of disconnect reasons
...is in 1.4.24 to 21 (call rejected) as defined in RFC 3398. For me this is a big issue because my dial plan will look for alternative termination in the event of network error (e.g. reason 3 or 21 which is resulting call status ?CONGESTION?) but will not do so for all normal terminations (16, Normal Termnation, 17 Busy, 18 No Answer).
Thanks,
Harel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100802/73c7c907/attachment-0001.htm