similar to: [GreenDragon] will be restarted 10:30PDT Today

Hello, Green Dragon is currently having trouble letting go of open file descriptors. We all have those days where it's just hard to let something go. We are going to put her to sleep for a bit, perform a little maintenance magic and see if we can't get those pesky file descriptors to close for good. Planning to restart the system at 10:30PDT today (August 20,2018). We will post a

Hello, Green Dragon will need to be restarted in order to apply security updates and plugin patches. The system will be restarted at 09:30 PDT. Thank you for your patience and cooperation. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180429/9a8dbdcf/attachment.html>

Hello, Green Dragon will need to be restarted in order to apply security updates and plugin patches. The system will be restarted at 22:40 PDT. Thank you for your patience and cooperation. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180513/96cee27e/attachment.html>

Hi, The backup is taking much longer than anticipated. I will notify the list as soon as the system is back on-line. Thanks. Respectfully, Mike Edwards On Thu, Dec 29, 2016 at 8:51 PM, Mike Edwards <mike at sqlby.me> wrote: > Hi, > Green Dragon is going to be down for about an hour while we perform some > system maintenance. We hope to not need the entire hour and will notify

Hi, Green Dragon has been experiencing some unfortunate network issues as of late. Currently we have several CI nodes offline and are working to bring them back up. We are going to take this opportunity to take the entire system down and bring it back up. I will update with further information as it becomes available. Thanks for your patience and understanding. Respectfully, Mike Edwards

Hi, Green Dragon will be down for maintenance for about the next hour or so while I apply some plugin security patches and perform a Jenkins Core update. I’ll update this email when I am done working and everything is back on-line. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL:

We are experiencing a system error on Green Dragon and need to reboot the system ASAP. We will reboot and bring the system back on-line in the next 45 minutes. Sorry for any inconvenience, thank you for your patience. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL:

Good Afternoon, I will need to restart Green Dragon at 14:15PST today in order to apply a few security patches and to reconfigure the network proxy to fix a minor bug we have discovered. I anticipate the reboot will take just a few minutes and I hope to have the system back up by 14:30PST. Sorry for any interruption and thanks for your patience and understanding. Respectfully, Mike Edwards

Hi, We need to upgrade our Jenkins instance on Green Dragon. We will do so this evening, Wednesday the 7th at 18:30 PST. Email and IRC notifications will be down for a bit after we bring the system back up to allow time for testing. We will notify the list once we are back in full operation. Thanks for your time. Respectfully, Mike Edwards -------------- next part -------------- An HTML

Hi, Green Dragon is going to be down for about an hour while we perform some system maintenance. We hope to not need the entire hour and will notify the list when the system is back on-line. Thank you for your patience and understanding. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL:

Good Morning, We will be restarting Green Dragon at 10:00PST today in order to apply security updates. Thank you for your patience and cooperation. Hope you all have a nice day. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180128/91e2630f/attachment.html>

Hello, We will be performing some routine maintenance on Green Dragon throughout the day today, beginning around 10:00PDT. The work is scheduled to be completed at approximately 17:00PDT this afternoon. We will make every effort to minimize any downtime. Hope you all have a pleasant day. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, We have resolved the instability issue with Green Dragon and have re-enabled IRC and email notifications. If you have made any commits within the previous twenty four hours, it would be greatly appreciated if you would check the build status on Green Dragon to see if your commit may be responsible for some of the build and test failures we are currently seeing on the bots. Thank you and

Hello, We have just re-enabled email and irc notifications on Green Dragon. It seems like the infrastructure related failures have been put to rest with the addition of a new switch to Green Dragon's environment. Hope you all have a nice day. Respectfully, Mike Edwards -------------- next part -------------- An HTML attachment was scrubbed... URL:

These ran to completion without error. :( > On Jan 12, 2016, at 3:23 PM, Chris Matthews <chris.matthews at apple.com> wrote: > > I’m running this on green-dragon-03 which is running OSX 10.10.5. > > /Users/buildslave/jenkins/sharedspace/clang-stage1-cmake-RA_workspace\@2/clang-build/bin/clang++ ../llvm/projects/compiler-rt/test/tsan/mmap_stress.cc -lpthread > while

On 01/12/2016 10:26 PM, Kostya Serebryany wrote: > Hi Tobias, > > What machine is that? > We have seen this and similar tests be flaky on older Linux kernels due > to kernel bug(s). > May I ask you to run the same test (just built with clang) on the same > machine for ~100000 times and see if it ever crashes? > > clang++

I have added a Jenkins check for this test, which explains why it fails on some builds. Can we change the test to keep its output? Will it just be blank anyways? > On Jan 20, 2016, at 1:23 PM, Kostya Serebryany <kcc at google.com> wrote: > > The test fails again:

On Wed, Jan 20, 2016 at 1:31 PM, Chris Matthews <chris.matthews at apple.com> wrote: > I worded that poorly, the Jenkins check I added will explain to the user > that we know this fails sometimes. > > On Jan 20, 2016, at 1:30 PM, Chris Matthews <chris.matthews at apple.com> > wrote: > > I have added a Jenkins check for this test, which explains why it fails on

Ah ha! I found crash reports: green-dragon-03:DiagnosticReports buildslave$ cat mmap_stress.cc.tmp_2016-01-19-231335_green-dragon-03.crash Process: mmap_stress.cc.tmp [95010] Path: /Users/USER/*/mmap_stress.cc.tmp Identifier: mmap_stress.cc.tmp Version: 0 Code Type: X86-64 (Native) Parent Process: bash [95004] User ID:

Hm, I tried to reproduce this as well, but unsuccessfully. From the crash report: EXC_I386_GPFLT means we’re dereferencing a non-canonical pointer, in this case “0x00486000000025df”. This happens at wrap_OSSpinLockLock+17, which is just after the prologue and just after calling cur_thread(). So I’d say it happens when we’re dereferencing the pointer returned by cur_thread(). On OS X, we’re