About Cloud Testing
Cloud Testing allows you to test your websites using real browsers – from the cloud.
It can be used for both Cross Browser Testing and Functional Testing.
For more information on the Cloud Testing service, visit www.cloudtesting.com.
Subscribers to the service can access the Cloud Testing customer portal is at portal.cloudtesting.com.
Thunderbird 3.0.4 Beta
Mozilla has released a beta of Tunderbird 3.0.4 – the final release is expected on the 30th March 2010
https://wiki.mozilla.org/Releases/Thunderbird_3.0.4
Firefox 3.6.2
Mozilla yesterday released a beta version of the Firefox 3.6 browser to fix several stability and security issues.
Firefox 3.6.2 has been released to Mozilla’s beta tester community, and includes several bug fixes such as crashes when using Adobe’s ClickMap add-on. Other problems reported by some users, such as there being no prompt to update extensions for the browser when Firefox was upgraded, have been fixed in the new version.
The beta isn’t aimed at all surfers, though changes will eventually be implemented in the full, stable version of Firefox 3.6.
You can download the Firefox 3.6.2 beta from the Mozilla website.
Firefox 3.6 was launched in January, with Firefox being the second-most popular browser after Microsoft’s Internet Explorer, though Microsoft’s dominance of the browser market is already being eroded after it was forced to offer everyone using it’s operating system the chance to switch to another browser – Opera has already reported a rise in the number of people using its browser as a consequence.
Apple Safari 4.0.5
Apple has released Safari 4.0.5 to address multiple vulnerabilities in ColorSync, ImageIO, PubSub, Safari, and WebKit. These vulnerabilities may allow a remote attacker to execute arbitrary code, cause a denial-of-service condition, obtain sensitive information, or bypass security restrictions.
US-CERT encourages users and administrators to review Apple article HT4070 and upgrade to Safari 4.0.5 to help mitigate the risks.
The Cloud Testing Agents have been updated to the latest release.
More Cloud Testing Agents added
To meet demand we’ve added more agents to our testing pool – let us worry about providing and looking after the service, letting you get on with what you do best – developing and running websites.
Windows updates applied to Cloud Testing Agents
The current release of Windows updates have been applied to all of the Cloud Testing Agents – see the Updates section.
Why run your own testing infrastructure when we can run it for you from the cloud?
Japanese Language installed onto Cloud Testing agents
In preparation for our new joint venture in Japan – Cloud Testing Japan (www.cloudtesting.jp), we have updated all of our agents (servers that run your tests for you) with Japanese.
Firefox 2.0 drops off the radar
We keep an active check on the browsers that our visitors use, mainly for interest, but today is the first day that there have been no visitors at all using Firefox 2.0.
We guess that in general if you’ve chosen Firefox, you keep up to date (assuming all your favorite add-ins work in the new version).
We still support Firefox 2.0 as part of our cross browser testing service, but are also seeing a drop off of people using it for testing their websites.
Version 3.6 has already risen to 21%, 3.5 is still 42% (probably people waiting for the add-ins to be updated) and 3.0 comes in at 4% – the next one to bite the dust we suspect.
Firefox 3.5.8 and Firefox 3.0.18
Firefox 3.5.8 and Firefox 3.0.18 address three critical flaws in the browsers’ Gecko rendering engines, the HTML parsers, and their implementations of web worker, an enhanced scripting functionality that lets
site developers shift JavaScript computations to a background thread to reduce the performance hit on Firefox’s user interface. The fixes are already in the 3.6 release.
Cloud Testing has updated it’s agents with the latest versions.
MySQL Community Server 5.1.44
MySQL Community Server 5.1.44, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.44 is recommended for use on production systems.
For an overview of what’s new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html
For information on installing MySQL 5.1.44 on new servers or upgrading to MySQL 5.1.44 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html
MySQL Server is available in source and binary form for a number of platforms from http://dev.mysql.com/downloads/
For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html
The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-44.html
Changes in MySQL 5.1.44
InnoDB Plugin Notes:
* This release includes InnoDB Plugin 1.0.6. This version is considered of Release Candidate (RC) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,
x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64.
Functionality added or changed:
* Replication: Introduced the –binlog-direct-non-transactional-updates server option. This option causes updates using the statement-based logging format to tables using non-transactional engines to be written directly to the binary log, rather than to the transaction cache.
Before using this option, be certain that you have no dependencies between transactional and non-transactional tables. A statement that both selects from an InnoDB table and inserts into a MyISAM table is an example of such a dependency. For more information, see Section 16.1.3.4,
“Binary Log Options and Variables.”
(Bug#46364: http://bugs.mysql.com/bug.php?id=46364)
See also Bug#28976: http://bugs.mysql.com/bug.php?id=28976,
Bug#40116: http://bugs.mysql.com/bug.php?id=40116.
Bugs fixed:
* Partitioning: When an ALTER TABLE … REORGANIZE PARTITION statement on an InnoDB table failed due to innodb_lock_wait_timeout expiring while waiting for a lock, InnoDB did not clean up any temporary files or tables which it had created. Attempting to reissue the ALTER TABLE statement following the timeout could lead to storage engine errors, or possibly a crash of the server.
(Bug#47343: http://bugs.mysql.com/bug.php?id=47343)
* Replication: In some cases, inserting into a table with many columns could cause the binary log to become corrupted.
(Bug#50018: http://bugs.mysql.com/bug.php?id=50018)
See also Bug#42749: http://bugs.mysql.com/bug.php?id=42749.
* Replication: When using row-based replication, setting a BIT or CHAR column of a MyISAM table to NULL, then trying to delete from the table, caused the slave to fail with the error Can’t find record in table.
(Bug#49481: http://bugs.mysql.com/bug.php?id=49481,
Bug#49482: http://bugs.mysql.com/bug.php?id=49482)
* Replication: When logging in row-based mode, DDL statements are actually logged as statements; however, statements that affected temporary tables and followed DDL statements failed to reset the binary log format to ROW, with the result that these statements were logged using the statement-based format. Now the state of binlog_format is restored after a DDL statement has been written to the binary log.
(Bug#49132: http://bugs.mysql.com/bug.php?id=49132)
* Replication: When using row-based logging, the statement CREATE TABLE t IF NOT EXIST … SELECT was logged as CREATE TEMPORARY TABLE t IF NOT EXIST … SELECT when t already existed as a temporary table. This was caused by the fact that the temporary table was opened and the results of the SELECT were inserted into it when a temporary table existed and had the same name.
Now, when this statement is executed, t is created as a base table, the results of the SELECT are inserted into it — even if there already exists a temporary table having the same name — and the statement is logged correctly.
(Bug#47418: http://bugs.mysql.com/bug.php?id=47418)
See also Bug#47442: http://bugs.mysql.com/bug.php?id=47442.
* Replication: Due to a change in the size of event representations in the binary log, when replicating from a MySQL 4.1 master to a slave running MySQL 5.0.60 or later, the START SLAVE UNTIL statement did not function correctly, stopping at the wrong position in the log. Now the slave detects that the master is using the older version of the binary log format, and corrects for the difference in event size, so that the slave stops in the correct position.
(Bug#47142: http://bugs.mysql.com/bug.php?id=47142)
* The SSL certificates in the test suite were about to expire. They have been updated with expiration dates in the year 2015.
(Bug#50642: http://bugs.mysql.com/bug.php?id=50642)
* The printstack function does not exist on Solaris 8 or earlier, which would lead to a compilation failure.
(Bug#50409: http://bugs.mysql.com/bug.php?id=50409)
* A user could see tables in INFORMATION_SCHEMA.TABLES without appropriate privileges for them.
(Bug#50276: http://bugs.mysql.com/bug.php?id=50276)
* Debug output for join structures was garbled.
(Bug#50271: http://bugs.mysql.com/bug.php?id=50271)
* The filesort sorting method applied to a CHAR(0) column could lead to a server crash.
(Bug#49897: http://bugs.mysql.com/bug.php?id=49897)
* sql_buffer_result had an effect on non-SELECT statements, contrary to the documentation.
(Bug#49552: http://bugs.mysql.com/bug.php?id=49552)
* In some cases a subquery need not be evaluated because it returns only aggregate values that can be calculated from table metadata. This sometimes was not handled by the enclosing subquery, resulting in a server crash.
(Bug#49512: http://bugs.mysql.com/bug.php?id=49512)
* The method for comparing INFORMATION_SCHEMA names and database names was nonoptimal and an improvement was made: When the database name length is already known, a length check is made
first and content comparison skipped if the lengths are unequal.
(Bug#49501: http://bugs.mysql.com/bug.php?id=49501)
* The MD5() and SHA1() functions had excessive overhead for short strings.
(Bug#49491: http://bugs.mysql.com/bug.php?id=49491)
* Mixing full-text searches and row expressions caused a crash.
(Bug#49445: http://bugs.mysql.com/bug.php?id=49445)
* Creating or dropping a table with 1023 transactions active caused an assertion failure.
(Bug#49238: http://bugs.mysql.com/bug.php?id=49238)
* mysql-test-run.pl now recognizes the MTR_TESTCASE_TIMEOUT, MTR_SUITE_TIMEOUT, MTR_SHUTDOWN_TIMEOUT, and MTR_START_TIMEOUT environment variables. If they are set, their values are used to set the –testcase-timeout, –suite-timeout, –shutdown-timeout, and –start-timeout options, respectively.
(Bug#49210: http://bugs.mysql.com/bug.php?id=49210)
Windows and IE 6, 7 & 8 updated with security patches.
Updates for Windows have been applied to all Cloud Testing Agents – see the Updates section for more details.