Re: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-ppc

2009-11-19 Thread Michael Tüxen
On Nov 18, 2009, at 10:42 PM, Stig Bjørlykke wrote:

 On 18. nov. 2009, at 20.54, buildbot-no-re...@wireshark.org wrote:
 
 The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark 
 (development).
 Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/583
 
 Does anyone know why this happends?  It looks like a timeout creating 
 libwireshark.
The system is a slow, old G4 MacMini which runs headless. I think some
bluetooth system is not performing well when there is not keyboard/mouse
via USB or Bluetooth.
I tried to improve  the configuration (switch off bluetooth) and rebooted
the system. Let's see if it helps.
Best regards
Michael
 
 
 -- 
 Stig Bjørlykke
 
 
 ___
 Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
 Archives:http://www.wireshark.org/lists/wireshark-dev
 Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
 

___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-ppc

2009-11-19 Thread Michael Tüxen
... due to a reboot.

Best regards
Michael

On Nov 19, 2009, at 12:15 PM, buildbot-no-re...@wireshark.org wrote:

 The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark 
 (development).
 Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/588
 
 Buildbot URL: http://buildbot.wireshark.org/trunk/
 
 Buildslave for this Build: osx-10.5-ppc
 
 Build Reason: 
 Build Source Stamp: 31015
 Blamelist: etxrab
 
 BUILD FAILED: failed failed slave lost
 
 sincerely,
 -The Buildbot
 
 ___
 Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
 Archives:http://www.wireshark.org/lists/wireshark-dev
 Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
 

___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-ppc

2009-11-18 Thread Stig Bjørlykke
On 18. nov. 2009, at 20.54, buildbot-no-re...@wireshark.org wrote:

 The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark 
 (development).
 Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/583

Does anyone know why this happends?  It looks like a timeout creating 
libwireshark.


-- 
Stig Bjørlykke


___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-ppc

2009-11-18 Thread Michael Tüxen
On Nov 18, 2009, at 10:42 PM, Stig Bjørlykke wrote:

 On 18. nov. 2009, at 20.54, buildbot-no-re...@wireshark.org wrote:
 
 The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark 
 (development).
 Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/583
 
 Does anyone know why this happends?  It looks like a timeout creating 
 libwireshark.
Let me have a look...

Best regards
Michael
 
 
 -- 
 Stig Bjørlykke
 
 
 ___
 Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
 Archives:http://www.wireshark.org/lists/wireshark-dev
 Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
 

___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


Re: [Wireshark-dev] buildbot failure in Wireshark (development) on OSX-10.5-ppc

2009-04-21 Thread Guy Harris

On Apr 21, 2009, at 10:35 AM, buildbot-no-re...@wireshark.org wrote:

 The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark  
 (development).
 Full details are available at:
 http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/957

 Buildbot URL: http://buildbot.wireshark.org/trunk/

 Buildslave for this Build: osx-10.5-ppc

 Build Reason:
 Build Source Stamp: HEAD
 Blamelist: etxrab,guy

 BUILD FAILED: failed compile

The warnings are:

ranap.cnf:1490: warning: 'dissect_ranap_ForwardingIndication' defined  
but not used
ranap.cnf:764: warning: 'dissect_ranap_LastVisitedUTRANCell_Item'  
defined but not used
ranap.cnf:293: warning:  
'dissect_ranap_Source_ToTarget_TransparentContainer' defined but not  
used
ranap.cnf:303: warning:  
'dissect_ranap_SourceeNodeB_ToTargeteNodeB_TransparentContainer'  
defined but not used
ranap.cnf:483: warning: 'dissect_ranap_SRVCC_Operation_Possible'  
defined but not used
ranap.cnf:493: warning:  
'dissect_ranap_Target_ToSource_TransparentContainer' defined but not  
used
ranap.cnf:503: warning:  
'dissect_ranap_TargeteNodeB_ToSourceeNodeB_TransparentContainer'  
defined but not used

What causes unused dissector routines to be generated by asn2wrs?  I  
have the impression that there's stuff you can put into the .cnf file  
to suppress them, but is there a way for asn2wrs to recognize that  
something won't be used?
___
Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe