We need to talk process for a bit. Keeping the various Jenkins jobs in good working order requires significant resources. I'm more than happy to keep doing that, but if no-one is paying attention to the information those jobs provide, what is the point?
The situation for the past month (!) is that Mustella (main) has been failing some tests. More than 2 weeks ago, some Mustella (mobile) tests started failing as well. These are the failures: Main: all players: - gumbo/components/DataGrid/Properties/DataGrid_Properties_editable Editable_startItemEditorSesision_inValidParams Failed Timed out Main: 11.1/3.7 - gumbo/components/ListDragDrop/events/SparkDNDList_events ListAbcDND1_dragDrop Failed CompareBitmap(body:step 16) compare returned[object BitmapData] Mobile: all players - mobile/SkinnablePopupContainerSK/integration/SPUC_KeyboardEffects_CalloutButton SPUC_skEffects_initialresize_calloutbutton Failed AssertMethodValue (method cannot be shown)(body:step 10) method returned false, expected true - mobile/SkinnablePopupContainerSK/integration/SPUC_KeyboardEffects_CalloutButton_List SPUC_skEffects_initialresize_calloutbutton Failed AssertMethodValue (method cannot be shown)(body:step 10) method returned false, expected true Now, either these tests need to be changed to 'fit' any new features/fixes, or some commits need to be reverted. I think this needs to be done as soon as possible. I also think that we need a bit better discipline: commit, review and revert when a test fails. I'm looking into increasing the Mustella from a 'medium' to a 'large' instance, that should give us more frequent testing, but as it stands, the full suite of Mustella runs twice daily, so in any time zone there is plenty timely feedback on whether your commit broke something... EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
