search for: 8014

Hi Galina, It seems the 8014 build master is offline? Is that intentional? Should I move the bot back to 8011? http://lab.llvm.org:8014/ cheers, --renato

...(local 2005 1 ) Ringing Dial SIP/2005|20|t Zap/9-1 (sales s 2 ) Up Dial SIP/2000&SIP/2001&SIP/2003&SIP/2005|20|t Zap/29-1 (outbound-max s 1 ) Up Bridged Call Zap/5-1 Zap/5-1 (lec-pri 8014 1 ) Up Dial Zap/g2/8014 Zap/33-1 (outbound-max s 1 ) Up Bridged Call Zap/10-1 Zap/10-1 (lec-pri 8014 1 ) Up Dial Zap/g2/8014 Zap/26-1 (outbound-max s 1 ) Up Bridged Call Zap/2-1...

...'")',) We're running with --exec-multisample=3, so I think it should expect one result for each sample. I managed to submit the corresponding report.json [2] to a local, default (sqlite-based) LNT server. Any idea what the problem might be? Thanks, Diana [1] http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2397/steps/test-suite/logs/stdio [2] http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2397/steps/test-suite/logs/report.json

...t should expect >> one result for each sample. I managed to submit the corresponding >> report.json [2] to a local, default (sqlite-based) LNT server. >> >> Any idea what the problem might be? >> >> Thanks, >> Diana >> >> [1] http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2397/steps/test-suite/logs/stdio >> [2] http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2397/steps/test-suite/logs/report.json

Full_Name: Jonathan Paisley Version: 2.1.1 OS: Mac OS X 10.4.2 Submission from: (NULL) (81.178.107.67) I was following an example from library/grid/doc/grid.pdf ("Introduction to grid") and had the following code, where I'd mis-typed 1,3 instead of 1,2 as the first arguments to grid.layout. Sourcing this code causes the R GUI to crash. I've enclosed a partial backtrace from

...are 3 main problem areas: - building LLVM on Windows with Visual Studio - running a Windows buildbot - Running Windows in a cloud environment in a stable, reproducible and maintainable way So I'm looking for someone to help me to debug and fix the buildbot <http://lab.llvm.org:8014/builders/clang-x86-ninja-win10?numbuilds=200>and get it into a stable state. Links on the current state and the setup: - Builder <http://lab.llvm.org:8014/builders/clang-x86-ninja-win10?numbuilds=200> on staging with current list of failing tests - generic Visual Studio Docke...

Hi, The new LNT server instance http://lnt.llvm.org seems to fail in many cases. Any entrance to a 'Run page' (e.g. http://lnt.llvm.org/db_default/v4/nts/62475) and lately also many perf bots result submissions (e.g. http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio ) fails with: "500 Internal Server Error". Any ideas? Thanks, Elad --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain conf...

Hey all, It seems that the main buildmaster here is working fine http://lab.llvm.org:8011/ However, I have a 'connection refused' error whilst connecting to the staging buildmaster http://lab.llvm.org:8014/ Are you aware of this Victor and Galina? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170806/3b95cd5b/attachment.html>

...dfft, etc), so I doubt this is in any was a real time out due to code-gen issues. I imagine they're all at the edge already and the standard deviation is enough to get it past the limit often. Given that this is mostly noise, can you move this bot to the quiet build master (http://lab.llvm.org:8014/) so that you can continue to track it's progress without emailing people all the time? Once it's stable again, you can move it back to the main master. Thanks! --renato

Hi folks, It seems all LNT buildbots are broken due to the error: error: The 'six==1.9.0' distribution was not found and is required by LNT The module seems to be in version 1.10 and probably the old binary is no longer there. Do we really need it to be 1.9? Can't that be >1.9? cheers, --renato

...nce http://lnt.llvm.org <http://lnt.llvm.org/> seems to fail in many cases. > Any entrance to a ‘Run page’ (e.g. http://lnt.llvm.org/db_default/v4/nts/62475 <http://lnt.llvm.org/db_default/v4/nts/62475>) and lately > also many perf bots result submissions (e.g. http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio <http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio> ) fails with: > “500 Internal Server Error”. > > Any ideas? > > Thanks, Elad > ---------------...

...o, so the main problem is when using combination Asterisk 1.8.x (I have tried the last 1.8.9.0 also), and using lib java peers client, it is fail. This is the Full DEBUG log. I dont know what else to do, googling found no one with the similar problem. [Jan 28 23:03:32] DEBUG[1654]: chan_sip.c:8014 find_call: = Looking for Call ID: hDVA1Kyx-1327766611250 at lucidesktop.lan (Checking From) --From tag grUqFtoE --To-tag [Jan 28 23:03:32] DEBUG[1654]: acl.c:728 ast_ouraddrfor: For destination '192.168.2.159', our source address is '192.168.2.172'. [Jan 28 23:03:32] DEBUG[1654]: c...

Switched all but PPC, I don't have access to them. But they run the same script as sanitizer-x86_64-linux. http://lab.llvm.org:8014/#/waterfall?tags=sanitizer On Mon, 12 Oct 2020 at 19:19, Galina Kistanova <gkistanova at gmail.com> wrote: > We have a better version of AnnotatedCommand on the staging. It should be > a functional equivalent of the old one. > We need to stress test it well before moving to the pro...

...long time to run, close to the timeout, so that it's too long some times, and others not. 2. There is a random codegen/instrumentation problem that only shows some times. Address randomization could be an issue, here. I've moved it to the silent build master for now: http://lab.llvm.org:8014/builders/clang-cmake-aarch64-full cheers, --renato

On 18 August 2016 at 15:21, Renato Golin <renato.golin at linaro.org> wrote: > On 18 August 2016 at 14:32, Alex Bradbury <asb at asbradbury.org> wrote: >> Good question, I didn't mention buildbots in this RFC as from a quick >> look at http://lab.llvm.org:8011/builders it didn't look like >> early-stage architecture ports tend to have one, and as you say

...y notifications. The both have the same set of builders and it's easy to switch a slave between them. To add slave/builder please add your slave and builder to zorg, but point your slave to silent master: use lab.llvm.org:9994 instead of lab.llvm.org:9990 It's address: http://lab.llvm.org:8014 Thanks Galina On Fri, May 27, 2016 at 1:04 PM, Asiri Rathnayake < asiri.rathnayake at gmail.com> wrote: > I was hoping to avoid the trouble of having to setup a master buildbot. > > But may be it's just easier to run Zorg as-is locally alongside the > buildslave. I'l...

On Wed, Jul 31, 2019 at 11:37 AM Vitaly Buka via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I have no idea how. > Are there particular problems? Now it should be quite. > Console has a bunch of stale builders which are even less useful. > LLVM has a silent build master that does not send email. When Nico added the gn build, apparently we promised not to set up builders

...013/opening_balance/post", host: "rs" 2007/08/14 22:19:40 [error] 1720#0: *129 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.102, server: factory, URL: "/opening_balance/post", upstream: " http://127.0.0.1:8014/opening_balance/post ", host: "rs" 2007/08/14 22:20:40 [error] 1720#0: *129 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.102 , server: factory, URL: "/opening_balance/post", upstream: " http://127.0.0.1:8...

I was hoping to avoid the trouble of having to setup a master buildbot. But may be it's just easier to run Zorg as-is locally alongside the buildslave. I'll give that a go. Cheers, / Asiri On Fri, May 27, 2016 at 8:45 PM, Yaron Keren <yaron.keren at gmail.com> wrote: > You don't really need to use the llvm builders infrastructure, just setup > a local jenkins (or

Our Flang-aarch64 buildbots just won't connect to the main Buildbot master anymore. I switched them to the staging buildbot master instead and it seems fine for now. Is there anything that we can/should tweak at our end? http://lab.llvm.org:8014/#/waterfall?tags=flang -Andrzej On 08/10/2020 00:31, Galina Kistanova via cfe-dev wrote: > They are online now - http://lab.llvm.org:8011/#/waterfall?tags=sanitizer > > AnnotatedCommand has severe design conflict with the new buildbot. > We have changed it to be safe and still do som...