search for: flaki

lld/test/ELF/invalid/symtab-sh-info.s (check-lld-elf) is recently flaky on Windows, e.g. https://reviews.llvm.org/harbormaster/unit/view/192869/ http://45.33.8.238/win/27684/step_10.txt It fails like every 3 or 4 builds. Could someone with a Windows machine check what is going on? Is that due to output non-determinism (just my guess) in yaml2obj.exe? -------------- next part -------------- An

Thanks for taking a look. The flaky ASan test failure in the OP was stage1 so it sounds like there may be multiple problems :( -- Sean Silva On Sun, Jun 12, 2016 at 7:32 AM, Benjamin Kramer <benny.kra at gmail.com> wrote: > I threw all the sanitizers I had access to on this test and didn't > find anything. The merging uses threads so I can't rule out > nondeterminism.

I threw all the sanitizers I had access to on this test and didn't find anything. The merging uses threads so I can't rule out nondeterminism. It's strange that it only happens on ppc64le and only on stage 2, so an actual miscompile wouldn't surprise me either. On Sun, Jun 12, 2016 at 4:26 PM, Sean Silva <chisophugis at gmail.com> wrote: > Also, `Clang Tools ::

Hello, We are experiencing flaky behavior from rsync when attempting to rsync directories/files to a server in Penang. Several times the job seems to 'hang' and never completes. Penang then is therefore missing a lot of required cad files. Have any of you experienced the same thing and what did you do to fix the problem? Does anyone know of a better tool to use? We chose

My change 225282 broke an asan test [1], but by the time I got around to trying to revert it, I noticed that the test had started passing. Moreover, it seems to have been "fixed" by 225291 which at least does not seem related to the breakage directly. I'm puzzled now -- is the failing asan test flaky? Should I still revert 225282? Thank you for your time! [1]:

I think we've hit a record in the number of inline replies, here... :) Let's start fresh... Problem #1: What is flaky? The types of failures of a buildbot: 1. failures because of bad hardware / bad software / bad admin (timeout, disk full, crash, bad RAM) 2. failures because of infrastructure problems (svn, lnt, etc) 3. failures due to previous or external commits unrelated to the

On 9 October 2015 at 19:02, David Blaikie <dblaikie at gmail.com> wrote: > Where "software" here is presumably the OS software Yes. This is the real noise, one that we cannot accept. > I think that misses the common usage of the term "flaky test" (or do the > tests themselves end up other (1) or (2)?) or flaky tests due to flaky > product code (hash

This just failed again: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/1579 Bill, could you take a look at this? This is like the 3rd time I've been incorrectly pinged by this buildbot due to this issue. -- Sean Silva On Mon, Jun 13, 2016 at 8:07 PM, Sean Silva <chisophugis at gmail.com> wrote: > Thanks for taking a look. The flaky ASan test failure in the

Hi Bill, just a heads up but this bot seems to have spuriously failed on a build that only pulled in my commit r272505 which is unrelated. http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883 -- Sean Silva -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160612/8b2c4493/attachment.html>

According to https://reviews.llvm.org/D88348#2344466, that diff should fix the failure. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Fāng-ruì Sòng via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Fāng-ruì Sòng <maskray at google.com> Date: Tuesday, November 10, 2020 at 10:13 PM To: LLVM Developers Mailing List <llvm-dev at lists.llvm.org> Cc: Nico

Hey all, Has anyone ever had problems with flaky behaviour when registering softphones dynamically with asterisk? I'm working with Kphone and having problems getting consistent results with registration. When Kphone is able to register, asterisk reports -- registered SIP '2001' at XXX.XXX.XXX.XXX port 5060 where asterisk sees [2001] in sip.conf as [2001]

One strategy I use for our flaky bots is to have them email me only. If the failure is real, then I forward the email to who ever I find on the blame list. For a flaky build, this is least you can do. For our flaky builds I know how and why they are flaky, some person that gets email does not. This is also a great motivator to help me know what is wrong, and how to fix it. By default, all new

...L DP43BF (John R Pierce) 11. Re: logrotate.d - reload vs restart (Nico Kadel-Garcia) 12. Re: Problems with motherboard support? INTEL DP43BF (John Plemons) 13. Re: logrotate.d - reload vs restart (Frank Cox) 14. Re: logrotate.d - reload vs restart (Bill Campbell) 15. E1000 eth1 link flakiness - causes?? (E Westphal) 16. Re: E1000 eth1 link flakiness - causes?? (Ryan Wagoner) 17. Re: E1000 eth1 link flakiness - causes?? (E Westphal) 18. Re: E1000 eth1 link flakiness - causes?? (fred smith) 19. Re: E1000 eth1 link flakiness - causes?? (Frank Cox) 20. Re: E1000 eth1 link flak...

I looked at this a bit a while back when you first asked but I didn't see anything obviously wrong. Benjamin, at least one of the referenced failures was on BE powerpc64. I don't remember if that one (http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883) failed on stage 1 or 2 and the results pages are no longer available. BTW, I tried testing the same revision many

Hello, I'm not sure if I'm asking this question in the right place, so please redirect me if there's a better list. I recently set up a Windows 10 guest on an Arch Linux host with libvirt and KVM/Qemu, using IOMMU to enable GPU passthrough. I followed this guide to set up the VM: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF The problem that I'm having is

Hi all! Just become a xen user and this is my first post to the list. Just installed xen on SuSE 9 Enterprise and got it working. It is great! I love it. The bridging seems to be a little flaky when the domU''s are running dhcp. It seems that when the domU''s start up, the dhcp client is not ready to get the IP. The domU''s come up without an IP. After rebooting the

On 08/26/2015 04:12 PM, Renato Golin via llvm-dev wrote: > On 26 August 2015 at 15:07, Davide Italiano <davide at freebsd.org> wrote: >> I see frequent timeouts on this bot -- can the timeout be increased? > > Hi Davide, > > Increasing the timeout is not ideal. We need to fix the problem in a > different way. > > Our other ARM bots are using CMake 3.2 + Ninja

> On Oct 7, 2015, at 3:28 PM, Renato Golin <renato.golin at linaro.org> wrote: > > On 7 October 2015 at 23:20, Chris Matthews <chris.matthews at apple.com> wrote: >> For instance, a build that fails with a ninja error, will say so, same with a >> svn failure or a Jenkins exception. > > Will these get mailed to developers? Or admins? Unfortunately, Jenkins

I set up a simple BlindUp and BlindDown div that works seamlessy in Firefox but doesn''t work as smoothly in IE. When blinding down, the whole div flashes and then Blinds down. The same thing when blinding up. Is this something that is fixable? _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org

...onal issues with winbind on the Samba servers 'hanging' while trying to query the AD server, but I think this is unrelated. (Subject for another post). I'd like some confirmation from people who understand the workings of the authentication systems involved, whether this occasional DFS flakiness is *certainly* a problem with the Windows server, or if there's any way in which the Samba servers might be related to the problem. When a client querys a MS DFS tree, does the Windows server do any sort of authentication checking to see if that user is allowed to access a given DFS share...