Site Overlay

Tag: mozmill

CategoriesMozilla

Firefox Automation report – week 19/20 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 19 and 20. Highlights When we noticed that our Mozmill-CI production instance is quickly filling up the /data partition, and having nearly no space left to actually run Jenkins, Henrik did a quick check, and has seen that the problem were the update jobs. Instead of producing log files with about 7MB in size, files with more than 100MB each were present. Inspecting those files revealed that the problem were allContinue readingFirefox Automation report – week 19/20 2014

CategoriesMozilla

Firefox Automation report – week 17/18 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 17 and 18. Highlights In one of the last automation reports I mentioned that we wanted to finish up the already in-progress Mozmill tests for Firefox Metro. With lots of work mostly done by Daniel we were finally able to close all the bugs as fixed. Now everyone is back on top of our new quarterly goals. To allow new contributors of the mozmill-tests repository to pick appropriate reviewers for theirContinue readingFirefox Automation report – week 17/18 2014

CategoriesMozilla

Firefox Automation report – week 15/16 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 15 and 16. Highlights To be able to support the new update path for Firefox Beta users via a final release candidate on the beta channel, we had to update our update testruns with Mozmill in the mozmill-automation repository. Further we also had to add support for this update path in Mozmill CI. Cosmin spend his time on those patches, and finally we got those out and active. That means fromContinue readingFirefox Automation report – week 15/16 2014

CategoriesMozilla

Firefox Automation report – week 13/14 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 13 and 14. Highlights Finally we were able to upgrade our mozmill-ci production system to Mozmill 2.0.6. The only caveat is that we had to disable one test for cleaning history to prevent the always occurring Flash crash on Windows. This week Henrik was able to land the first fixes for broken TPS tests. Together with Andrei we were able to fix 4 of them. Also we had our first AutomationContinue readingFirefox Automation report – week 13/14 2014

CategoriesMozilla

Firefox Automation report – week 11/12 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 11 and 12. Highlights After Henrik got started on updating the TPS test framework for Firefox Sync tests, he got it into a state that it is working with the new Firefox Accounts feature coming with Firefox 29.0. For details please see bug 966434. Fixing the backward compatibility for the old Sync authentication is his next step. With the release of Mozmill 2.0.6 and the initial support of handling crashes, weContinue readingFirefox Automation report – week 11/12 2014

CategoriesMozilla

Firefox Automation report – week 9/10 2014

By Admin

In this post you can find an overview about the work happened in the Firefox Automation team during week 9 and 10. I for myself was a week on vacation. A bit of relaxing before the work on the TPS test framework should get started. Highlights In preparation to run Mozmill tests for Firefox Metro in our Mozmill-CI system, Andreea has started to get support for Metro builds and appropriate tests included. With the help from Henrik we got Mozmill 2.0.6 released. It contains a helpful fix for waitForPageLoad(), whichContinue readingFirefox Automation report – week 9/10 2014

CategoriesMozilla

Firefox Automation report – week 7/8 2014

By Admin

The current work load is still affecting my time for getting out our automation status reports. The current updates are a bit old but still worth to mention. So lets get them out. Highlights As mentioned in my last report, we had issues with Mozmill on Windows while running our restart tests. So during a restart of Firefox, Mozmill wasn’t waiting long enough to detect that the old process is gone, so a new instance has been started immediately. Sadly that process failed with the profile already in use error.Continue readingFirefox Automation report – week 7/8 2014

CategoriesMozilla

Firefox Automation report – week 5/6 2014

By Admin

A lot of things were happening in weeks 5 and 6, and we made some good progress regards the stability of Mozmill. Highlights The unexpected and intermittent Jenkins crashes our Mozmill CI system was affected with are totally gone now. Most likely the delayed creation of jobs made that possible, which also gave Jenkins a bit more breath and not bomb it with hundreds of API calls. For the upcoming release of Mozmill 2.0.4 a version bump for package dependencies was necessary for mozdownload. So we released mozdownload 1.11. SadlyContinue readingFirefox Automation report – week 5/6 2014

CategoriesMozilla

Firefox Automation report – week 3/4 2014

By Admin

Due to the high work load and a week of vacation I was not able to give some updates for work done by the Firefox Automation team. In the next days I really want to catch up with the reports, and bring you all on the latest state. Highlights After the staging system for Mozmill CI has been setup by IT and Henrik got all the VMs connected, also the remaining Mac Minis for OS X 10.6 to 10.9 have been delivered. That means our staging system is complete andContinue readingFirefox Automation report – week 3/4 2014

CategoriesMozilla

Firefox Automation report – week 1/2 2014

By Admin

I promised to keep up with our updates over the last week but given a major breakage in the freshly released version of Mozmill 2.0.4, I had a full week of work to get the fix out. I promise that during this week I will write reports for the weeks in January. Highlights With the new year our team has been reorganized and we are part of the Mozilla QA team again. That means we will have a way closer relationship to any feature owner, and also working towards inContinue readingFirefox Automation report – week 1/2 2014

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close