Downloads
Release notes
Introduced in 6.x-2.14-beta5:
Fixed highlighting for passed tests on qa.d.o test result pages.
Introduced in 6.x-2.14-beta4:
Issue #1909128 by jthorson: Added verbosity to test setup 'clear checkout' step
Issue #1905842 by jthorson: Colorize active testing status in environment table
Updated pifr_client_cron_test_processess_get() to properly respect D8 'core' directory restructuring
Rollback of Issue #1903118.
Introduced in 6.x-2.14-beta3:
Issue #1903118: Add a 'prepare environment' step before requesting the next test
- This issue clears the checkout and review directories prior to picking up a test, so that issue in setting up the testing environment do not result in testing failures.
Issue #1903888: Reset cancellation status (if it exists) when recording a result
Introduced in 6.x-2.14-beta2:
Added "Send cancellation requests to testbot for commit-triggered branch re-tests."
Added "Verify that result exists before attempting to delete in pifr_server_result_delete()."
Introduced in 6.x-2.14-beta1:
Fixed "unqueue button should not appear on tests sent to a testbot"
Issue #1878482 by jthorson: Ignore result if no environment status found for a given client
Add #ignore_lines and #cache to coder args to eliminate notices
Issue #1828632 by jthorson: Add ability to cancel active tests on testbot
The 'cancel tests' functionality was implemented with the addition of a new xmlrpc function on both client and server. While actively testing, testbots will now report back to qa.drupal.org the current test_id and environment which is being tested on that client. If this does not match with what qa.d.o is expecting (in the pifr_environment_status table), or if an administrator has requested that testing on that particular testbot be cancelled, then a flag is sent back to with the response asking the testbot to reset testing and pick up the next test from the queue.
The 6.x-2.14 release also changes the functionality of the 'retest' and 'requeue' buttons on the tools page for a given test. Where these buttons used to queue up every applicable environment for a given test, they now operate on a single environment at a time.