Modernizing Testbot Initiative meeting July 7th

Agenda for this meeting was:

• Reviewing the need for enabling php 5.5 testing on the old test bots so they can be a point of comparison for regressions with the new DrupalCI bots.
• Setting up a new env on qa.d.o for php 5.5
• Testing the patch to raise minimum version
• Pushing out in time for next beta release
• Reviewing the DrupalCI MVP hitlist
• #2517958: Improve consistency of Postgres environments
• Some solid improvements made but more to go.
• Need to continue to coordinate with core devs to tighten these up.
• Improvements in stability on sqlite may carry over - related issues: 2524426 and 2524426
• #2517980: [DrupalCI Integration] Enable patch testing
• Essentially ready to enable
• Needs to be updated a bit for the newly separated jenkins job
• Semi-blocked by xml parsing/container stability but essentially ready
• #2518008: Improve the XML output/parsing of the test runner
• Implemented as a publish plugin for DCI
• Basically ready to deploy
• Logically groups tests by test-group - 'assertion count' appears lower, but will actually be more consistent
• Some edge-case parsing issues for certain errors, probably acceptable
• #2518026: Notify core maintainers of test failures with a diff against the previous nights result
• Has been blocked by splitting jenkins jobs (now unblocked)
• Can be configured in Jenkins now for short term
• Long term via d.o or sent in as parameters to test job
• #2518056: Need the ability to cancel a test job
• Current jenkins job kill does not kill container
• May need to update containers to poll for whether the pid should continue running- kill if not.
• Once issues are resolved, will provide certain core devs with jenkins access for canceling jobs as short term solution for this
• jthorson’s Accelerate Update
• Essentially finished with defining artifacts by job type and implementing gathering of artifacts - needs testing
• Need to merge with the junit xml changes before working further on publishing.
• Going to move on to syntax checking next