search for: nastily

...;> > > I've asked Daniel Dunbar to increase the timeout on this machine. Every > build which requires libLTO to be rebuilt will fail, but because it's doing > an incremental build the later builds may succeed so long as libLTO doesn't > change. It's flapping pretty nastily because of that. > > So Daniel, please take this as a reminder to *really* increase the timeout > instead of just filing it away into your todo list :) Sure, sure, blame me not all the people making LLVM fatter (err, maybe that is also me)! :) Timeout upped to 30m, let me know if you see...

...got stuck with a weird behavior of pretty: pretty(c(-1,1),n=1) yields -2, 0, 2 instead of the desired result -1 1. Likewise, pretty(c(-2,2),n=1) yields -5, 0, 5 instead of the desired result -2 2. With n=0, the result is the same, while with n=2 everything is as documented. This behavior nastily messed up some of my cube plots. Is there any chance that this can be fixed? Regards, Ulrike -- View this message in context: http://www.nabble.com/Strange-behavior-of-pretty-tf4744337.html#a13566672 Sent from the R devel mailing list archive at Nabble.com.

...'s nag messages. > I've asked Daniel Dunbar to increase the timeout on this machine. Every build which requires libLTO to be rebuilt will fail, but because it's doing an incremental build the later builds may succeed so long as libLTO doesn't change. It's flapping pretty nastily because of that. So Daniel, please take this as a reminder to *really* increase the timeout instead of just filing it away into your todo list :) Nick

A short while ago I reported a network interruption while performing a YUM update on a server. A check of the logs as recommended by a list member indicated that the update process had succeeded. However, I am now encountering the following problem on that same server and my nastily suspicious mind is trying to tell me that the previous event and this situation are somehow related. > Downloading Packages: > Running Transaction Test > Finished Transaction Test > Transaction Test Succeeded > Running Transaction > warning: waiting for transaction lock > err...

...Daniel Dunbar to increase the timeout on this machine. Every >> build which requires libLTO to be rebuilt will fail, but because it's >> doing >> an incremental build the later builds may succeed so long as libLTO >> doesn't >> change. It's flapping pretty nastily because of that. >> >> So Daniel, please take this as a reminder to *really* increase the >> timeout >> instead of just filing it away into your todo list :) > > Sure, sure, blame me not all the people making LLVM fatter (err, maybe > that is also me)! :) > &gt...

Just received this: The Buildbot has detected a new failure of llvm-ppc-linux on llvm. Full details are available at: http://google1.osuosl.org:8011/builders/llvm-ppc-linux/builds/3229 Buildbot URL: http://google1.osuosl.org:8011/ Buildslave for this Build: nick1 Build Reason: Build Source Stamp: 84759 Blamelist: ofv BUILD FAILED: failed compile Apparently the problem was a warning at

...erable software is there really a benefit? > > LTS distributions back port necessary patches Then the OP should be able to update to a dovecot that doesn't have the issue, right? -- 'And I suppose you know what sound is made by one hand clapping, do you?' said the holy man nastily. YES. CL. THE OTHER HAND MAKES THE AP.

Hello, I run Konfabulator under OS X 10.3.7 with a proxy connection to the internet and I use an IP address identifyer widget. It shows from time to time incoming and outgoing traffic on a Samba server(s). This appearance is extremely brief. I don?t know anything about Samba and have never knowingly used it on my machine. Can you fill me in on this? Is this malicious activity? Thanks, pc

> with broken or vulnerable software is there really a benefit? LTS distributions back port necessary patches

I do not have a strong opinion on the naming of the various size functions, or on how to deal with APInt's of sizes that are not multiples of a byte. I do think loading and storing more bytes than necessary is generally a bad idea, especially if you're getting uninitialized bits. (If you incorrectly cross a page boundary, you might fault, for one thing. Watch out for packed

Hey all, I''m thinking about moving my 2.0.7 install over to 3.0.0 for eventual use in a production environment. Two questions: 1) Do people think 3.0.0 is ready for production - or is it just a testing/unstable playpen? 2) What do I have to change - just the xen-2.0.7.gz for do I have to recompile the dom0/domU kernels too? Cheers, Matthew Walster

Hello, My question is not related to NSD in particular, but I have seen here on the list a lot of people that work for TLDs and other Registrars and Registry operators I thought it would be a good place to ask this question. It is about DNS though, not completely off topic :). I have encountered in my DNS studies a few name servers that let you transfer zones they are authoritative for. The

Now that I'm working on codegen support for arbitrary precision integers (think i36 or i129), I've hit the problem of what getTypeSize and friends should return for such integers (the current implementations seem to me to be wrong). However it's not clear to me how getTypeSize and friends are defined. There seem to be several possible meanings for the size of a type (only talking

...mUs are VPN gateways running the 2.4.30 kernel with openswan and openvpn. Because of the openvpn, but are privileged domains but the only device driver configured in the kernel is the openvpn tun/tap adapter. We first noticed problems during shutdown in that the last domU to shutdown crashed very nastily when closing openvpn. We could see this even when manually stopping the domUs. We surmised that the problem was we had tun0 and tun1 defined in both domains and killing them in one must be killing them in another. We renamed those tun adapters in the second domain to tun10 and tun11 and that pro...