search for: nights

Hello I have what is probably a very simple grouping question however, given my limited exposure to R, I have not found a solution yet despite my research efforts and wild attempts at what I thought "might" produce some sort of result. I have a very simple list of integers that range between 1 and 24. These correspond to hours of the day. I am trying to create a grouping of Day and

Hello, I have some satellite tag time-at-depth (TAD) frequency data that I would like some help with. The data was transmitted via satellite as percent time spent in each of 7 depth bins (0m, 0-1m, 1-10m, 10-50m etc.), binned over 6-hour intervals. I categorized each row of data corresponding to a date and time into summer vs. winter, and day vs. night, and then summed and averaged the given

hello everybody, i just commited a pkgsrc for dovecot nightly cvs-snapshots to the pkgsrc-wip repository for NetBSD - this will hopefully go into base pkgsrc, soon. please see http://pkgsrc-wip.sourceforge.net/ on how to obtain pkgsrc-wip. ----- Forwarded message from Tom Hensel <tomhensel at users.sourceforge.net> ----- Date: Sun, 22 Feb 2004 11:18:52 -0800 From: Tom Hensel

Hy there, i have a centos (4.?) Box with nightly yum update enabled. Last night, it did an upgrade to 4.7 leading to several problem i.e. not respawning the dhcrelay, which is needed on this box. Can I control the update policy not to upgrade to new releases in the nightly updates? I would like do to nightly updates, but make release upgrades manual (I get a new kernel, so I have to reboot

I forgot to remove some crud from the configure script and it caused some of the nightly testers to fail last night. The problem has already been fixed. Part of the problem was that it took 2 hours to get a commit through to CVS last night and the nightly tester had already started by that time. Something needs to be done about the late night high load situation on zion (backups?) Reid

All, We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform. Directions to set up a tester are here: http://llvm.org/docs/TestingGuide.html#nightly These directions could be improved of course. If you have any questions, I will be happy to assist you in

After fixing nested () problem manual run nighttest finished successfully with one remarkable logged problem: INITIALIZED CVS Root = :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm BuildDir = /home/wanderer/pkg/build/llvm/night/build WebDir = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD Prefix = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD/2004-09-06

> x86 FreeBSD: > * hasn't run with changes yet I manually start script. I use this options (+ -verbose now for testing) /home/wanderer/pkg/build/llvm/src/llvm/utils/NightlyTest.pl -parallel -enable-linscan -noexternals -noremove :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm /home/wanderer/pkg/build/llvm/night/build

On Thu, 19 May 2005, Reid Spencer wrote: > I forgot to remove some crud from the configure script and it caused > some of the nightly testers to fail last night. The problem has already > been fixed. Part of the problem was that it took 2 hours to get a commit > through to CVS last night and the nightly tester had already started by > that time. Something needs to be done about the

Okay, I'll have to fix NightlyTest.pl not to use shell script syntax that isn't universal. Look for a commit soon. Reid. On Sun, 2004-09-05 at 13:31, Vladimir Merzliakov wrote: > > Bash 2.05b on Linux handles this fine. I was asking what > > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > > Perhaps you can: > > > >

That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >

Hello, On Jun 3, 2008, at 08:52 , Tanya Lattner wrote: > All, > > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. I think I might be able to set up a nightly tester for Linux x86 (32- bit). Although I've been following LLVM for

Asterisk 1.2.13 I am trying to figure out the best way for a night bell at work. Note: I have no spare buttons available on the phones. But I do have two lines and two park positions as buttons. Option 1 (easiest and the one I just implemented) When asterisk is in night mode, Connect to IVR, List all options and then if they dial 0 or timeout, ring every phone in the

I'm fairly new to Asterisk, so please bear with me if this is silly question. I'd like to run a script on my server that would take the "Call now to order" banner off my website automatically when I put my phone system on night. I can handle the webserver side of things, but I don't know where to begin on the Asterisk side of things - can a simple script be run to

I've uploaded the 2.0 pre-release to this location: http://llvm.org/prereleases/2.0/ If you have free time and would like to help test this release, please download the appropriate tarballs from the website. Here are a few ways you can help test this release: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run

Hello list! Tanya Lattner wrote: > We are in desperate need of linux x86 testers (32 or 64 bit). If you > could set one up, the LLVM project would be very grateful. Right now > we have virtually no testers covering this platform. I've run the test last night to see how long it takes, and I can afford to cronjob it for the night. I didn't quite realize it would automatically

On 8 January 2013 04:49, Duncan Sands <baldrick at free.fr> wrote: > While this should be investigated, > I'm tempted to just move everything over to LNT instead... > That's the latent bugs that David mentioned. I agree we should have LNT and LNT+LTO and possibly other configurations in the future. Regarding your buildbots, gcc12 is easy to replace by LNT, because the

I've noticed that my nightly tester doesn't seem to be reporting the results of running llvm-test, only build warnings and make check. Checking with -verbose shows that it's running the test suite, so I don't quite understand what's going on. Looking at http://llvm.org/nightlytest/ shows that none of the other Linux testers are reporting test suite results either.

Based on James suggestion to use the DB functions I made the following and thought it might be nice to share: ; exten => s,1,DBget($Night=GlobalSettings/Night) ; if not night jump to +101 exten => s,2,Goto(closed,s,1) ;Night has been set, we're closed exten => s,102,Goto(open,s,1) ;Night has not been set so we are open ; ; night settings ; calling 6502 toggles the Night-settings ;

Last night's nightly test has numerous new failures that can be attributed to the bug 122 changes. All these failures are related to the use of an outdated cfrontend build. The simple solution is to recompile the cfrontend. I ran into this also when I was testing the changes. The problem is that the bytecode read/written by the cfrontend is using an incompatible (partially between 1.2 and