["Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>]

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.
		CVPACK : fatal error CK1024: ringbuffer.obj cannot use program database c:\svn\wireshark\vc60.pdb : signatures do not match
		LINK : warning LNK4027: CVPACK error
		NMAKE : fatal error U1077: 'link' : return code '0x1'
		Stop.

Well, it didn't fail, so I'm not sure why that's happening for me.  At least it seems to successfully compile if I simply retry.  Strange though ... and annoying.  Regardless, I did notice a few other things with the buildbots that I thought I would mention:
 
1) The Windows buildbot is red due to the tshark test failing.  I looked at the Solaris and Ubuntu buildbots and perhaps the only reason why they're not also red is because the Solaris buildbot doesn't seem to run any tests and the Ubuntu buildbot skips almost all of the tshark tests.  Perhaps those tests should not be skipped?
 
2) The Windows buildbot does not report any warnings when creating an installer, whereas I get the following two warnings:
  LangString "MUI_UNTEXT_COMPONENTS_TITLE" is not set in language table of language English
  LangString "MUI_UNTEXT_COMPONENTS_SUBTITLE" is not set in language table of language English

I believe the reason I get the warnings and the Windows buildbot doesn't is because I'm using the latest version of NSIS, namely version 2.30 whereas the Windows buildbot is using version 2.17.  Perhaps it's time for an NSIS upgrade on the buildbot?  And then a fix of the two warnings above too.
 
3) The Solaris buildbot doesn't test all options.  Perhaps it should?  For example:
                     Install setuid : no
                   Build lua plugin : no
                   Build rtp_player : no
                        Use threads : no
             Build profile binaries : no
               Use GNU ADNS library : no
               Use SMI SNMP library : no

4) The Ubuntu buildbot doesn't test all options.  Perhaps it should?  For example:
                     Install setuid : no
                   Build lua plugin : no
                   Build rtp_player : no
                        Use threads : no
             Build profile binaries : no
             Use SSL crypto library : no

5) Neither the Solaris not the Ubuntu buildbots test creating an rpm (via make rpm-package) or test creating a source rpm (via make srpm-package).  Perhaps they should?  I create both Windows installers and Linux rpm's and I have run into problems with creating rpms in the past, so personally, I would be in favor of having those tests added to the suite.
 
6) The OSX buildbot doesn't test all options.  Perhaps it should?  For example:
                     Install setuid : no
                   Build lua plugin : no
                   Build rtp_player : no
                        Use threads : no
             Build profile binaries : no
                   Use pcre library : no
               Use GNU ADNS library : no
               Use SMI SNMP library : no
             Use GNU crypto library : no
             Use SSL crypto library : no
                 Use gnutls library : no
 
7) The OSX buildbot doesn't appear to build whatever equivalent installer and/or rpm would be needed to install on a MAC.  (Sorry, I don't know much about the MAC so I have no idea what to call it.)  Anyway, it'd probably be a good idea for it to do so as well, wouldn't it?
 
Regards,
Chris
 

-----------------------------------------
This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are
not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.