; *Subject:* Re: [Wireshark-dev] Buildbots
>
>
>
>
>
> On Thu, Nov 19, 2015 at 5:59 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
> There's also the:
>
>
>
> 2.0 buildbot - https://buildbot.wireshark.org/wireshark-2.0/waterfal
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Dario Lombardo
Sent: den 20 november 2015 10:52
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Buildbots
On Thu, Nov 19, 2015 at 5:59 PM, Graham Bloice
mailto:graham.blo
On 20 November 2015 at 09:51, Dario Lombardo
wrote:
>
> On Thu, Nov 19, 2015 at 5:59 PM, Graham Bloice <
> graham.blo...@trihedral.com> wrote:
>
>> There's also the:
>>
>> 2.0 buildbot - https://buildbot.wireshark.org/wireshark-2.0/waterfall
>> 1.12 buildbot - https://buildbot.wireshark.org/wires
On Thu, Nov 19, 2015 at 5:59 PM, Graham Bloice
wrote:
> There's also the:
>
> 2.0 buildbot - https://buildbot.wireshark.org/wireshark-2.0/waterfall
> 1.12 buildbot - https://buildbot.wireshark.org/wireshark-1.12/waterfall
> Debian LTS buildbot -
> https://buildbot.wireshark.org/wireshark-lts/wate
There's also the:
2.0 buildbot - https://buildbot.wireshark.org/wireshark-2.0/waterfall
1.12 buildbot - https://buildbot.wireshark.org/wireshark-1.12/waterfall
Debian LTS buildbot - https://buildbot.wireshark.org/wireshark-lts/waterfall
These are all listed on the develop page -
https://www.wires
As you said, petri-dish is triggered by core devs for unmerged gerrit
changes to test them before merging. Master is triggered on every merge to
build the actual git master branch.
On Thu, Nov 19, 2015 at 11:45 AM, Dario Lombardo <
dario.lombardo...@gmail.com> wrote:
> I've found 2 different buil
I've found 2 different buildbot projects for wireshark
https://buildbot.wireshark.org/petri-dish/
and
https://buildbot.wireshark.org/wireshark-master/
Can anyone explain me the difference? I've understood that petri-dish is
manually triggered by core-devs from gerrit. Who triggers the
wireshark
On 7/1/13 6:50 PM, Evan Huus wrote:
> The Solaris/SPARC and Windows7 trunk buildbots are in a strange state
> where they have several stale builds stuck permanently at the svn
> update step. I have not been able to cancel these builds from the
> regular UI (the request seems to succeed, but the bui
The Solaris/SPARC and Windows7 trunk buildbots are in a strange state
where they have several stale builds stuck permanently at the svn
update step. I have not been able to cancel these builds from the
regular UI (the request seems to succeed, but the builds are not
removed from the list).
I'm not
The last revision any of the buildbots seem to have built is 41145
whereas 41183 is the last commit. Everything's green, but nothing seems
to be happening (according to the waterfall display).
Clicking "force build" seems to work.
_
The Windows-XP-x86 and Ubuntu-10.04-x64 buildbots both appear to be stuck.
Their status indicates "building", but there's been no activity for some time.
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wi
Maynard, Chris wrote:
> I was looking at the Windows buildbot status to see if the compiling step
> would fail at the same place as it fails for me, namely here:
>
>
> Generating Code...
> Linking dumpcap.exe
> link @C:\DOCUME~1\cmaynard\LOCALS~
I was looking at the Windows buildbot status to see if the compiling step would
fail at the same place as it fails for me, namely here:
Generating Code...
Linking dumpcap.exe
link @C:\DOCUME~1\cmaynard\LOCALS~1\Temp\nmi02488.
13 matches
Mail list logo
