These are still happening occasionally. I dug out my XP-32 virtualbox instance but have not been able to reproduce.
Tangentially, running the test suite from cygwin I get the following failure (after the test the build-bot keeps failing on): 5 Suite: Unit tests 5.1 Step: exntest suite-unittests.sh: line 32: nmake: command not found "exntest" Failed! make ../epan/exntest failed Which seems to imply I ought to be running the tests from the visual studio command prompt (in order to have nmake), but of course it doesn't interpret shell scripts. What am I missing? Thanks, Evan On Sun, Mar 17, 2013 at 5:59 AM, <buildbot-no-re...@wireshark.org> wrote: > The Buildbot has detected a new failure on builder Windows-XP-x86 while > building Wireshark (development). > Full details are available at: > http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86/builds/4536 > > Buildbot URL: http://buildbot.wireshark.org/trunk/ > > Buildslave for this Build: windows-xp-x86 > > Build Reason: scheduler > Build Source Stamp: 48347 > Blamelist: etxrab > > BUILD FAILED: failed test.sh > > sincerely, > -The Buildbot > > > > ___________________________________________________________________________ > Sent via: Wireshark-commits mailing list <wireshark-comm...@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-commits > Unsubscribe: https://wireshark.org/mailman/options/wireshark-commits > > mailto:wireshark-commits-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
