archive-info.com » INFO » H » HSKUPIN.INFO

Total: 368

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Review of automation work – Q4 2015 | hskupin.info
    also package them into the common tests zip archive for use in mozmill ci Details about all that can be found on bug 1212609 But please be aware that we still use the Github repository as integration repository I regularly mirror the code to hg which has to happen until we can also use the test package for localized builds and update tests Beside all that there were also a couple of mozharness fixes necessary So I implemented a better fetching of the tooltool script added the uninstall feature and also setup the handling of crash symbols for firefox ui tests Finally the addition of test package support finished up my work on mozharness for Q4 in 2015 During all the time I was also sheriffing our test results on Treeherder e g mozilla central because we are still Tier 3 level and sheriffs don t care about it Mozmill CI Our Jenkins based CI system is still called mozmill ci even it doesn t really run any mozmill tests anymore We decided to not change its name given that it will only be around this year until we can run all of our tests in TaskCluster But lots of changes have been landed which I want to announce below We followed Release Engineering and got rid of the OS X 10 8 testing That means the used Mac minis were ready to get re imaged with OS X 10 11 The transition worked seamlessly Enhancements for test report submission to Treeherder by switching over to Hawk credentials and more understandable group names and symbols Preparation of all the machines of our supported platforms OSX 10 6 10 9 10 10 10 11 Ubuntu 14 04 Windows XP 7 8 1 to be able to handle mozharness driven tests Implemented and updated scripts to run firefox ui tests via mozharness and to allow Treeherder to fully parse our logs Addons Tools I also had some time to work on supporting tools Together with the help of contributors we got the following done mozdownload Release of mozdownload 1 18 1 and 1 19 to cope with the move of builds to AWS Nightly Tester Tools Porting back changes from the NTT fork called Utilu Nightly Tester Tools Memchaser Thanks to the tireless efforts from Szabolcs Hubai we got Memchaser working again in latest Firefox builds So all in all it was a productive quarter with lots of things accomplished I m glad that we got all of this done Now in Q1 it will continue and more interesting work is in front of me which I m excited about I will announce that soon in my next blog post Until then I would like to give a little more insight into our current core team for Firefox automation A picture taken during our all hands work week in Orlando early in December shows Syd Maja myself and David Lets get started into 2016 with lots of ideas discussions and enough energy

    Original URL path: http://www.hskupin.info/2016/01/09/review-of-automation-work-q4-2015/ (2016-05-01)
    Open archived version from archive


  • Results of the Firefox Automation Survey | hskupin.info
    question with Mostly So it s a clear indication what I already thought and which clearly needs action on our side to be more communicative Doing this might also bring more people into our active projects so mentoring would be much more valuable and time effective as handling any drive by projects which we cannot fully support A request for the type of news we should do more is definitely for latest changes and code landings from contributors This will ensure people feel recognized and contributors will also know each others work and see the effectiveness in regards of our project goals But also discussions about various automation related topics as mentioned already above are highly wanted Other topics like quarterly goals and current status updates are also wanted and we will see how we can do that We might be able to fold those general updates into the Engineering Productivity updates which are pushed out twice a month via the A Team Planet Also there is a bit of confusion about the Firefox Automation team and how it relates to the Engineering Productivity team formerly A Team Effectively we are all part of the latter and the virtual Automation team has only been created when we got shifted between the A Team and QA Team forth and back This will not happen anymore so we agreed on to get rid of this name All in all there are some topics which will need further discussions I will follow up with another blog post soon which will show off our plans for improvements and how we want to work to make it happen automation QA survey Post navigation Previous Post Survey about sharing information inside the Firefox Automation team Next Post Automation Survey Follow up Logging In Profile cancel Sign

    Original URL path: http://www.hskupin.info/2015/12/03/results-of-the-firefox-automation-survey/ (2016-05-01)
    Open archived version from archive

  • jenkins | hskupin.info
    Firefox ESR31 is no longer supported To lower the amount of machines we have to maintain and to getting closer what s being run on Buildbot we stopped running tests on Ubuntu 14 10 Means we only run on Ubuntu LTS releases from now on Also we stopped tests for OS X 10 8 The nodes will be re used for OS X 10 11 once released We experienced Java crashes due to low memory conditions of our Jenkins production master again This was kinda critical because the server is not getting restarted automatically After some investigation I assumed that the problem is due to the 32bit architecture of the VM Given that it has 8GB of memory a 64bit version of Ubuntu should have been better used So we replaced the machine and so far everything looks fine Totally surprising we had to release once more a bugfix release of Mozmill This time the framework didn t work at all due to the enforcement of add on signing So Mozmill 2 0 10 2 has been released automation continuous integration firefox jenkins marionette mozmill Software Mozilla Firefox Automation report Q2 2015 August 11 2015 Henrik Skupin 5 Comments It s been a while since I wrote my last Firefox automation report so lets do another one to wrap up everything happened in Q2 this year As you may remember from my last report the team has been cut down to only myself and beside that I was away the whole April Means only 2 months worth of work will be covered this time In general it was a tough quarter for me Working alone and having to maintain all of our infrastructure and keeping both of our tests Mozmill and Marionette green was more work as expected But it still gave me enough time to finish my two deliverables Ensure better visibility of Firefox UI test results for sheriffs and developers by uploading them to treeherder Finalize features for Firefox UI update tests and help to get them running on RelEng hardware Firefox UI Test Results on Treeherder With the transition of Mozmill tests to Marionette we no longer needed the mozmill dashboard Especially not since nearly no job in our Mozmill CI is running Mozmill anymore Given that we also weren t happy with the dashboard solution and the usage of couchdb under the hood I was happy that a great replacement exist and our Marionette tests can make use of Treeherder is the new reporting system for tests being run in buildbot continuous integration Because of that it covers all products and their appropriate supported branches That s why it it s kinda perfect for us Before I was able to get started a bit of investigation had to be done and I also checked some other projects which make use of treeherder reporting That information was kinda helpful even with lots of undocumented code Given that our tests are located outside of the development tree in its own Github repository some integration can be handled more loosely compared to in tree tests With that respect we do not appear as Tier 1 or Tier 2 but results are listed under the Tier 3 level which is hidden by default But that s fine given that our goal was to bring up reports to treeherder first Going into details will be a follow up task For reporting results to Treeherder the Python package treeherder client can be used It s a collection of different classes which help with authentication collecting job details and finally uploading the data to the server It s documentation can be found on readthedocs and meanwhile contains a good number of example code which makes it easier to get your code implemented Before you can actually upload reports the names and symbols of the groups and jobs have to be defined For our tests I have chosen the three group symbols Fu Ff and Fr Each of those stays for F irefox UI Tests and the first letter of the testrun name We currently have updates functional and remote As job name the locale of Firefox will be used That results in an output like the following Whether jobs are passing or failing it is recommended to always add the log files as generated by running the tests to the report It will not happen via data URLs but as artifacts with a link to an upload location In our case we make use of Amazon S3 as storage service With all the pieces implemented we can now report to treeherder and covering Nightly Aurora Developer Edition Beta and Release builds As of now reporting only happens against the staging instance of Treeherder but soon we will be able to report to production If you want to have a sneak peak how it works just follow this link for Nightly builds More details about Treeherder reporting I will do later this quarter when the next pieces have been implemented Firefox UI Update Tests under RelEng My second deliverable was to assist Armen Zambrano in getting the Firefox UI Update tests run for beta and release builds on Release Engineering infrastructure This was a kinda important goal for us given that until now it was a manually triggered process with lots of human errors on our own infrastructure That means lots of failures if you do not correctly setup the configuration for the tests and a slower processing of builds due to our limited available infrastructure So moving this out of our area made total sense Given that Armen had already done a fair amount of work when I came back from my PTO I majorly fixed issues for the tests and the libraries as pointed out by him All that allowed us to finally run our tests on Release Engineering infrastructure even with a couple of failures at the beginning for the first beta But those were smaller issues and got fixed quickly Since then we seem to have good results If you want to have a look in how that works you should check the Marionette update tests wiki page Sadly some of the requirements haven t been completely finished yet So the Quality Engineering team cannot stop running the tests themselves But that will happen once bug 1182796 has been fixed and deployed to production Oh and if you wonder where the results are located Those are not getting sent to Treeherder but to an internal mailing list as used for every other automation results Other Work Beside the deliverables I got some more work done Mainly for the firefox ui tests and mozmill ci While the test coverage has not really been increased I had a couple of regressions to fix as caused by changes in Firefox But we also landed some new features thankfully as contributed by community members Once all that was done and we agreed to have kinda stable tests new branches have been created in the repository That was necessary to add support for each supported version of Firefox down to ESR 38 0 and to be able to run the tests in our Mozmill CI via Jenkins More about that you will find below The only task I still haven t had time for yet was the creation of proper documentation about our tests I hope that I will find the time in Q3 Mozmill CI got the most changes in Q2 compared to all the former quarters This is related to the transition from Mozmill tests to Marionette tests More details why we got rid of Mozmill tests can be found in this post With that we decided to get rid of most of the tests and mainly start from scratch by only porting the security and update tests over to Marionette The complete replacement in Mozmill and all its jobs can be seen on issue 576 on Github In detail we have the following major changes Run all jobs with Marionette beside Firefox ESR 31 0 which is not supported by Marionette and ondemand update jobs because they still have to be run by Quality Engineering Reduced number of platforms We got rid of Windows Vista Ubuntu 14 10 and OS X 10 7 whereby the latter machines have been re used for OS X 10 10 No usage of a pre configured environments anymore but creating it from fresh for each test run by installing Python packages from the internal PyPI mirror Sending test results to treeherder and giving public access for everyone Stopped sending emails for failures to our mozmill ci mailing list in favor of having treeherder results All changes in Mozmill CI can be seen on Github Last but not least we also had two releases of mozdownload in Q2 Both had a good amount of features included For details you can check the changelog I hope that gave you a good quick read on the stuff I was working on last quarter Maybe in Q3 I will find the time to blog more often and in more detail Lets see automation ci continuous integration jenkins marionette mozmill Mozilla Firefox Automation report week 47 48 2014 January 14 2015 Henrik Skupin 1 Comment In this post you can find an overview about the work happened in the Firefox Automation team during week 47 and 48 Highlights Most of the work during those two weeks made by myself were related to get Jenkins http jenkins ci org upgraded on our Mozmill CI systems to the most recent LTS version 1 580 1 This was a somewhat critical task given the huge number of issue as mentioned in my last Firefox Automation report On November 17th we were finally able to get all the code changes landed on our production machine after testing it for a couple of days on staging The upgrade was not that easy given that lots of code had to be touched and the new LTS release still showed some weird behavior when connecting slave nodes via JLNP As result we had to stop using this connection method in favor of the plain java command This change was actually not that bad because it s better to automate and doesn t bring up the connection warning dialog Surprisingly the huge HTTP session usage as reported by the Monitoring plugin was a problem introduced by this plugin itself So a simple upgrade to the latest plugin version solved this problem and we will no longer get an additional HTTP connection whenever a slave node connects and which never was released Once we had a total freeze of the machine because of that Another helpful improvement in Jenkins was the fix for a JUnit plugin bug which caused concurrent builds to hang until the former build in the queue has been finished This added a large pile of waiting time to our Mozmill test jobs which was very annoying for QA s release testing work especially for the update tests Since this upgrade the problem is gone and we can process builds a lot faster Beside the upgrade work I also noticed that one of the Jenkins plugins in use it s actually the XShell plugin failed to correctly kill the running application on the slave machine in case of an job is getting aborted The result of that is that following tests will fail on that machine until the not killed job has been finished I filed a Jenkins bug and did a temporary backout of the offending change in that plugin Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 47 and week 48 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 47 and week 48 automation ci jenkins mozmill Mozilla Firefox Automation report week 45 46 2014 December 19 2014 Henrik Skupin Leave a comment In this post you can find an overview about the work happened in the Firefox Automation team during week 45 and 46 Highlights In our Mozmill CI environment we had a couple of frozen Windows machines which were running with 100 CPU load and 0MB of memory used Those values came from the vSphere client and didn t give us that much information Henrik checked the affected machines after a reboot and none of them had any suspicious entries in the event viewer either But he noticed that most of our VMs were running a very outdated version of the VMware tools So he upgraded all of them and activated the automatic install during a reboot Since then the problem is gone If you see something similar for your virtual machines make sure to check that used version Further work has been done for Mozmill CI So were finally able to get rid of all the traces for Firefox 24 0ESR since it is no longer supported Further we also setup our new Ubuntu 14 04 LTS machines in staging and production which will soon replace the old Ubuntu 12 04 LTS machines A list of the changes can be found here Beside all that Henrik has started to work on the next Jenkins v1 580 1 LTS version bump for the new and more stable release of Jenkins Lots of work might be necessary here Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 45 and week 46 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 45 and week 46 automation ci jenkins mozmill windows Mozilla Firefox Automation report week 43 44 2014 December 18 2014 Henrik Skupin Leave a comment In this post you can find an overview about the work happened in the Firefox Automation team during week 43 and 44 Highlights In preparation for the QA wide demonstration of Mozmill CI Henrik reorganized our documentation to allow everyone a simple local setup of the tool Along that we did the remaining deployment of latest code to our production instance Henrik also worked on the upgrade of Jenkins to latest LTS version 1 565 3 and we were able to push this upgrade to our staging instance for observation Further he got the Pulse Guardian support implemented Mozmill 2 0 9 and Mozmill Automation 2 0 9 have been released and if you are curious what is included you want to check this post One of our major goals over the next 2 quarters is to replace Mozmill as test framework for our functional tests for Firefox with Marionette Together with the A Team Henrik got started on the initial work which is currently covered in the firefox greenlight tests repository More to come later Beside all that work we have to say good bye to one of our SoftVision team members October the 29th was the last day for Daniel on the project So thank s for all your work Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 43 and week 44 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda the video recording and notes from the Firefox Automation meetings of week 43 and week 44 automation ci firefox jenkins marionette mozmill testing Mozilla Firefox Automation report week 25 26 2014 July 17 2014 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 25 and 26 Highlights June the 11th was actually the last Automation Training day for our team in Q3 About the results you can read here We will implement some changes for the next quarter when we most likely want to host 2 of them Henrik finally got the time to upgrade our Mozmill CI systems to the lastest LTS version of Jenkins There were a bit of changes necessary but in general all went fine this time and we can see some great improvements Especially the long delays when sending out job results seem to be gone Further Henrik investigated the slow behavior with the mozmill ci production master when it is under load e g QA runs ondemand update tests for releases of Firefox The main problem stays with Java which is taking up about 100 of the CPU Because of this the integrated web server cannot serve pages in a timely manner Adding a 2nd CPU to this node gave us way better response times Given that the new version of Ubuntu came out already in April we want to have our Mozmill tests also run on that platform version So we got new VM spun up by IT which we now have to puppetize and bring online But this may still take a bit given the remaining blockers for using PuppetAgain While talking about Puppet we got the next big change reviewed and landed With bug 1021230 we now have our own user account which can be customized to our needs And that s what we totally need given that our infrastructure is so different from the Releng one Also for TPS we made progress so the new TPS CI production machine came online Yet it cannot replace the current CI due to still a fair amount of open blockers but hopefully by end of July we should be able to turn the switch Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 25 and week 26 Meeting Details If you are interested in further details

    Original URL path: http://www.hskupin.info/tag/jenkins/ (2016-05-01)
    Open archived version from archive

  • Automation Survey Follow-up | hskupin.info
    but instead utilize the mozilla tools list Also because this is the recommended list for the Engineering Productivity team we are all part of and discussions will reach a larger audience So please subscribe to this list via Google Groups or Email For status updates about our current activities we started to use standu ps last quarter It seems to work pretty well for us and everyone else is welcome to also post updates to our automation project section If you are interested in those updates then read through that list or simply subscribe the page in your RSS reader Please also note that from now on there will be no Firefox Automation reports anymore Instead I will reduce the amount of different contents and only write about projects I worked on So keep an eye out to not miss those automation Mozilla QA Post navigation Previous Post Results of the Firefox Automation Survey Next Post Review of automation work Q4 2015 Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow up comments by email Notify me of new posts by email 2 Replies 0 Comments 2 Tweets 0 Facebook 0 Pingbacks Last reply was 3 months ago Planet Ateam View 3 months ago Henrik Skupin Automation Survey Follow up https t co weXBvLlwLt Reply PlanetFeeds View 3 months ago Henrik Skupin Automation Survey Follow up As promised in my last post about the automation survey results I https t co LAWjitP9r1 Reply Photostream January 2016 M T W T F S S Dec Feb 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

    Original URL path: http://www.hskupin.info/2016/01/05/automation-survey-follow-up/ (2016-05-01)
    Open archived version from archive

  • Mozilla | hskupin.info
    issues in mozdownload So as result we have released mozdownload 1 9 last week That fixed the last remaining blocker and we will have the l10n tests running on staging soon Over the last couple of weeks we were monitoring the memory usage of Jenkins a lot That happened not only in the browser but also more important for the whole system on the server side too As we noticed the Java process has a really high heap memory usage Beside that we had a couple of annoying issues around which caused some of our testruns to early abort So Henrik put a lot of work in getting Jenkins upgraded to the latest LTS Long Term Support version Given that this was a big jump for our really outdated Jenkins version a lot of work had to be spent in testing everything Also because nearly all of the Jenkins plugins which we make use of had updates available and had a slightly different format of the XML configuration all our static files had to be updated too But by early last week we were able to push those bits to our staging server and running that version of Jenkins for a week hasn t brought up any kind of regression That s great To finish up the work Henrik published all bits and bytes to our production machine yesterday We will continue observing the memory usage and let you know if the situation got better Beside that we made a couple of changes to our list of available nodes for the mozmill ci cluster As of last week we brought our Windows 8 1 nodes 3x 32bit 3x 64bit online for preliminary testing Given that all went well and no further issues have been seen they are now fully integrated into jobs triggered by Pulse notifications Further we have replaced our existent Ubuntu 12 10 nodes with the current release of Ubuntu 13 04 That means we run our tests on Ubuntu 12 04 LTS and Ubuntu 13 04 for both 32bit and 64bit now As requested by Mozilla QA we have to run more tests for localized beta and release candidate builds of Firefox That will help us to finally stop releasing broken l10n builds like Firefox 24 0b1 to our users For all locales covered by our tests we do now check for start up failures like the XML parsing error for the main window So Henrik pushed a patch to production which enabled tests to be run for the first 10 most used locales of Firefox Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development firefox Mozilla mozmill testing Mozilla Mozdownload 1 9 released August 29 2013 Henrik Skupin 2 Comments Oh my It happened again And here it is Another release of mozdownload with a couple of new features included As a regular user please let us know if all is working well or if you want to see some new features included Below you can find an overview about the main features in mozdownload 1 9 Tinderbox builds can be downloaded by timestamp now For linux64 the 64 bit and not the 32 bit installer gets downloaded Support for the stub installer on Windows has been added Better error messages are displayed All details for this release can be seen in the changelog Thanks again to everyone who was involved in this release automation firefox Mozilla Software Mozilla Automation Development report week 33 2013 August 20 2013 Henrik Skupin 3 Comments Starting from today the Automation Development team wants to publish weekly reports about the work happened in the previous week Reason is that similar to other groups we want to offer everyone more insight into our projects and that we might find even more community members who are interested to help us and learn new stuff at the same time If you have comments or proposals to the style and contents please let us know Highlights Beginning of last week we promoted Andrei Eftimie who is working for our team as a Softvision contractor from Romania as peer for our Mozmill Tests repository That happens in regard of all his contribution in the last couple of months So if you are looking for a reviewer of your patch you can flag him from now on Congratulations again Dave Hunt got the performance tests running on the Leo devices now Those are testing the cold load times and fps of the applications under test Over the past couple of weeks we detected a lot of application disconnects while running the Mozmill tests for Firefox under the Mozmill CI system As it has been turned out notifications bubbles from application updates could be the problem and especially the new update overlay screen for Windows 8 updates The latter completely blocked our testing So Henrik Skupin re configured all existing nodes and templates by disabling any automatic update checks Bug 900860 Since that has been done no further application disconnects have been observed Lets cross the fingers that this will stay that way We noticed a massive disconnect of slave nodes in our Mozmill CI cluster early last week At the same time the response time of our Jenkins master was drastically slow Henrik investigated the problem and identified that our current VM is not able to handle the memory load with 2GB of memory So we increased the memory to 4GB which indeed stopped the swapping process of consuming about 60 cpu load nearly all the time Henrik will continue to watch the current memory consumption over the next weeks Further we will upgrade our Jenkins installation to the latest LTS version soon once all blockers are fixed Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad automation automation development Mozilla Mozilla Join our Make sure your code works session MozCamp September 5 2012 Henrik Skupin Leave

    Original URL path: http://www.hskupin.info/tag/mozilla/ (2016-05-01)
    Open archived version from archive

  • Survey about sharing information inside the Firefox Automation team | hskupin.info
    ensure that we do not make use of the wrong communication channels depending where most of our readers are I have setup a little survey It will only take you a minute to go through but it will help us a lot to know more about the preferences of our automation geeks So please take that little time and help us The survey can be found here and is open until end of November 2015 https www surveymonkey com r 528WYYJ Thank you a lot automation Mozilla QA survey testing Post navigation Previous Post Firefox Automation report Q3 2015 Next Post Results of the Firefox Automation Survey Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow up comments by email Notify me of new posts by email 2 Replies 0 Comments 2 Tweets 0 Facebook 0 Pingbacks Last reply was 5 months ago Planet Ateam View 5 months ago Henrik Skupin Survey about sharing information inside the Firefox Automation team https t co yivvroagv4 Reply PlanetFeeds View 5 months ago Henrik Skupin Survey about sharing information inside the Firefox Automation team Within the Firefox Automat https t co RbSeBEBLr5 Reply Photostream November 2015 M T W T F S S Oct Dec 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Recent Posts Review of Firefox desktop automation work Q1 2016 March 31 2016 Firefox Desktop automation goals Q1 2016 February 2 2016 Review of automation work Q4 2015 January 9 2016 Automation Survey Follow up January 5 2016 Results of the Firefox Automation Survey December 3 2015 Survey about sharing information inside the Firefox

    Original URL path: http://www.hskupin.info/2015/11/23/survey-about-sharing-information-inside-the-firefox-automation-team/ (2016-05-01)
    Open archived version from archive

  • survey | hskupin.info
    of all feel less informed about our current activities Another 33 answered this question with Mostly So it s a clear indication what I already thought and which clearly needs action on our side to be more communicative Doing this might also bring more people into our active projects so mentoring would be much more valuable and time effective as handling any drive by projects which we cannot fully support A request for the type of news we should do more is definitely for latest changes and code landings from contributors This will ensure people feel recognized and contributors will also know each others work and see the effectiveness in regards of our project goals But also discussions about various automation related topics as mentioned already above are highly wanted Other topics like quarterly goals and current status updates are also wanted and we will see how we can do that We might be able to fold those general updates into the Engineering Productivity updates which are pushed out twice a month via the A Team Planet Also there is a bit of confusion about the Firefox Automation team and how it relates to the Engineering Productivity team formerly A Team Effectively we are all part of the latter and the virtual Automation team has only been created when we got shifted between the A Team and QA Team forth and back This will not happen anymore so we agreed on to get rid of this name All in all there are some topics which will need further discussions I will follow up with another blog post soon which will show off our plans for improvements and how we want to work to make it happen automation QA survey Mozilla Survey about sharing information inside the Firefox Automation team November 23 2015 Henrik Skupin 2 Comments Within the Firefox Automation team we were suffering a bit in sharing information about our work over the last couple of months That mainly happened because I was alone and not able to blog more often than once in a quarter The same applies to our dev automation mailing list which mostly only received emails from Travis CI with testing results Given that the team has been increased to 4 people now beside me this is Maja Frydrychowicz Syd Polk and David Burns we want to be more open again and also trying to get more people involved into our projects To ensure that we do not make use of the wrong communication channels depending where most of our readers are I have setup a little survey It will only take you a minute to go through but it will help us a lot to know more about the preferences of our automation geeks So please take that little time and help us The survey can be found here and is open until end of November 2015 https www surveymonkey com r 528WYYJ Thank you a lot automation Mozilla QA survey testing Mozilla Software

    Original URL path: http://www.hskupin.info/tag/survey/ (2016-05-01)
    Open archived version from archive

  • Firefox Automation report – Q3 2015 | hskupin.info
    the tracking bug 1192369 Mozmill CI Our Jenkins instance got lots of updates for various new features and necessary changes All in all I pushed 27 commits which affected 53 files Here a list of the major changes Refactoring of the test jobs has been started so that those can be used for mozharness driven firefox ui tests later in Q4 The work has not been finished and will be continued in Q4 Especially the refactoring for report submission to Treeherder even for aborted builds will be a large change A lot of time had to be spent in fixing the update tests for all the changes which were coming in with the Funsize project of Release Engineering Due to missing properties in the Mozilla Pulse messages update tests could no longer be triggered for nightly builds Therefore the handling of Pulse messages has been completely rewritten to allow the handling of similar Pulse messages as sent out from TaskCluster That work was actually not planned and has been stolen me quite some time from other projects A separation of functional and remote tests didn t make that much sense Especially because both types are actually functional tests As result they have been merged together into the functional tests You can still run remote tests only by using tag remote similar for tests with local testcases by using tag local We stopped running tests for mozilla esr31 builds due to Firefox ESR31 is no longer supported To lower the amount of machines we have to maintain and to getting closer what s being run on Buildbot we stopped running tests on Ubuntu 14 10 Means we only run on Ubuntu LTS releases from now on Also we stopped tests for OS X 10 8 The nodes will be re used for OS X 10 11 once released We experienced Java crashes due to low memory conditions of our Jenkins production master again This was kinda critical because the server is not getting restarted automatically After some investigation I assumed that the problem is due to the 32bit architecture of the VM Given that it has 8GB of memory a 64bit version of Ubuntu should have been better used So we replaced the machine and so far everything looks fine Totally surprising we had to release once more a bugfix release of Mozmill This time the framework didn t work at all due to the enforcement of add on signing So Mozmill 2 0 10 2 has been released automation continuous integration firefox jenkins marionette mozmill Software Post navigation Previous Post Crusial SSD bug and firmware fix Next Post Survey about sharing information inside the Firefox Automation team Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow up comments by email Notify me of new posts by email 2 Replies 0 Comments 2 Tweets 0 Facebook 0 Pingbacks Last reply was 6 months ago Planet Ateam View

    Original URL path: http://www.hskupin.info/2015/10/20/firefox-automation-report-q3-2015/ (2016-05-01)
    Open archived version from archive