#WXWINDOW FINDFOCUS EXAMPLE SERIES#
#WXWINDOW FINDFOCUS EXAMPLE WINDOWS#

It looks like the culprit is GetAs() test, verify it. Leave only a single wxAny unit test disabled. To find out where exactly does this happen. This is the test that results in memory corruption in wxOSX PPC builds, try

Start bisecting GetAs() wxAny test itself. Something in GetAs() test definitely corrupts memory, but what? 00:29 VZ, revision 73955 Reduce the number of wxAny tests ran under wxOSX further. Disable it to allow theĮntire test suite to pass. Local ones (and sometimes in buildbot ones too).

This check keeps failing in buildbot builds even though it always passes in 01:22 VZ, revision 73957ĭisable a sporadically failing check in wxBitmapComboBox unit test. 15:22 VZ, revision 73958Įnable a few more tests in wxAnyTestCase::GetAs(). This test is used for several different classes, show the name of the classīeing tested when the assert in Editable() test fails. Show the name of the actually tested class in text entry unit tests. Version of libjpeg that uses wxjpeg_boolean instead of boolean as it doesn'tĭefine boolean at all in its headers, but just wxjpeg_boolean. This fixes compilation problem when using libtiff with the built-in modified M /wxWidgets/trunk/src/tiff/libtiff/tif_ojpeg.c.M /wxWidgets/trunk/src/osx/cocoa/nonownedwnd.mmĪpplying editor part of patch, see #15003 15:25 VZ, revision 73960.M /wxWidgets/trunk/src/osx/cocoa/combobox.mm.M /wxWidgets/trunk/include/wx/osx/cocoa/private.h.Revert r73959, the name of the control can be seen from the name of theįailing test case actually, so there is no need to include it in the message. Revert 'Show the name of the actually tested class in text entry unit tests.' Recognize them as running automatic tests too.Īlso show the name of the current system and user on startup to avoid such Some build slaves apparently run under 'buildbot' user and not 'buildslave', Recognize 'buildbot' user in IsAutomaticTest() too.

#WXWINDOW FINDFOCUS EXAMPLE SERIES#

This is part of the continuing series of commits to find out what results in 21:21 VZ, revision 73964Įnable yet more tests in wxAnyTestCase::GetAs(). So test for the former instead for the latter, see r73963. The buildbot slaves actually use 'sandbox' as the user name, not 'buildbot', Recognize 'sandbox' user as indicating automatic testing.

M /wxWidgets/trunk/src/osx/cocoa/window.mmĭeactivating r65382 see #12267 (which does not seem to happen anymore even without this change), fixes #14938, 21:19 VZ, revision 73966Įnable another test in wxAnyTestCase under OS X.

Initialize them always to avoid the warnings. Value but the compiler doesn't seem to take this into account, so just The variables are actually initialized in all cases if the enum has valid

M /wxWidgets/trunk/src/generic/timectrlg.cppįix spurious g++ warning about possibly uninitialized variable use.

#WXWINDOW FINDFOCUS EXAMPLE WINDOWS#

Use '-t' in runtests.bar used by Windows build slaves to get more informationĪbout the test failures, notably if they crash before completing. Use '-t' option when running buildbot tests under Windows. See r73957, this test keeps failing when running on a build slave, even though M /wxWidgets/trunk/tests/controls/textentrytest.cppĭisable the rest of Editable() test for wxBitmapComboBox.This seems to be the reason for the heap corruption in wxOSX PPC builds. More elements are added to wxMouseButton enum in the future.ĭisable double-to-float conversion tests in wxAny code. Unfortunately Clang intelligent flow analysis prevents us from using differentĪsserts for invalid parameter value and unhandled one, which could happen if M /wxWidgets/trunk/include/wx/mousestate.hįix harmless Clang warning about unreachable code.The problem was not related to float-to-double conversions in wxAny code, try Whack-a-mole with wxOSX/PPC unit tests continued. M /wxWidgets/trunk/tests/any/anytest.cpp.Changelog for wxWidgets (70435 changes): 01:04 VZ, revision 73973

Wxwindow findfocus example