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".
  • Firefox Automation report – Q2 2015 | hskupin.info
    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

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


  • hskupin.info | Mozilla, Photography and the Daily Life | Page 2
    marionette mozmill mozqa testing 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

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

  • hskupin.info | Mozilla, Photography and the Daily Life | Page 25
    Abschnitte aus der linken Sidebar musste ich dann erstaunt feststellen dass sich der IE an einem leeren h2 Element h2 verschluckt und nachfolgende Textteile falsch darstellt Nach dem hinzufügen eines seperaten schließenden Tags wird nun auch die rechte Sidebar so dargestellt wie es sein sollte Continue reading CSS Tweakin Webdesign Neue Farben November 1 2005 Henrik Skupin 6 Comments Nicht nur die Natur kann zu dieser schönen Zeit wieder Farbenpracht versprühen Endlich gibt es auch von meiner Seite Neuigkeiten Nach monatelanger Abstinenz und zugegebenermaßen wirklich schlechter Pflege meiner Webseiten war ein komplettes Redesign wirklich mehr als fällig Viele Details der bisherigen Implementierung waren einfach nicht mehr tragbar Dabei geriet allein schon die Aktualisierung von Inhalten oftmals regelrecht zur Farce Die Struktur an sich war auch einfach zu starr und unhandlich Zusätzlich schlichen sich immer mehr Probleme ein Angefangen von Fehlern in der Zeichenkodierung bis hin zu welche CSS Selektoren zur Verwendung kommen sollen Doch das soll endlich der Vergangenheit angehören Aufgrund von Zeitmangel wegen diverser Projekte und Erstellung von Patches für den demnächst kommenden Firefox 1 5 fiel mir die erste Entscheidung relativ leicht Die Fortführung meines bisherigen Systems kam auf keinen Fall in Frage Die Zeit die ich für die Erweiterung benötigen würde hab ich nicht und nutz sie dann doch lieber sinnvoller für andere Dinge Demnach war der Wunsch ein bereits fertiges CMS einzusetzen geboren Continue reading Neue Farben Posts navigation Previous 1 24 25 Photostream May 2016 M T W T F S S Mar 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 Recent Posts Review of Firefox desktop automation work Q1 2016 March 31 2016 Firefox Desktop automation goals Q1 2016 February 2

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

  • March | 2016 | hskupin.info
    mozmill ci once Firefox 45 0 and its ESR release were out Adding mach support for Firefox UI Tests on mozilla central was the next step to assist in running our tests Required arguments from before are now magically selected by mach and that allowed me to remove the firefox ui test dependency on firefox harness which was always a thorn in our eyes As final result I was even able to completely remove the firefox ui test package so that we are now free in moving our tests to any place in the tree In case you want to know more about our tests please check out our new documentation on MDN which can be found here https developer mozilla org en US docs Mozilla QA firefox ui tests Mozmill CI Lots of changes have been done to this project to accommodate the Jenkins jobs to all the Firefox UI Tests modifications Especially that I needed a generic solution which works for all existing Firefox versions The first real task was to no longer use the firefox ui tests Github repository to grab the tests from but instead let mozharness download the appropriate test package as produced and uploaded with builds to archive mozilla org It was all fine immediately for en US builds given that the location of the test packages json file is distributed along with the Mozilla Pulse build notification But it s not the case for l10n builds and funsize update notifications For those we have to utilize mozdownload to fetch the correct URL based on the version platform and build id So all fine A special situation came up for update tests which actually use two different Firefox builds If we get the tests for the pre build how can we magically switch the tests for the target version Given that there is no easy way I decided to always use the tests from the target version and in case of UI changes we have to keep backward compatibility code in our tests and Firefox Puppeteer This is maybe the most ideal solution for us Another issue I had to solve with test packages was with release candidate builds For those builds Release Engineering is not uploading nor creating any test archive So a connection had to be made between candidate builds and CI tinderbox builds As turned out the two properties which helped here are the revision and the branch With them I at least know the changeset of the mozilla beta mozilla release and mozilla esr branches as used to trigger the release build process But sadly that s only a tag and no builds nor tests are getting created Means something more is necessary After some investigation I found out that Treeherder and its Rest API can be of help Using the known tag and walking back the parents until Treeherder reports a successful build for the given platform allowed me to retrieve the next possible revision to be used with

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

  • Review of Firefox desktop automation work – Q1 2016 | hskupin.info
    always a thorn in our eyes As final result I was even able to completely remove the firefox ui test package so that we are now free in moving our tests to any place in the tree In case you want to know more about our tests please check out our new documentation on MDN which can be found here https developer mozilla org en US docs Mozilla QA firefox ui tests Mozmill CI Lots of changes have been done to this project to accommodate the Jenkins jobs to all the Firefox UI Tests modifications Especially that I needed a generic solution which works for all existing Firefox versions The first real task was to no longer use the firefox ui tests Github repository to grab the tests from but instead let mozharness download the appropriate test package as produced and uploaded with builds to archive mozilla org It was all fine immediately for en US builds given that the location of the test packages json file is distributed along with the Mozilla Pulse build notification But it s not the case for l10n builds and funsize update notifications For those we have to utilize mozdownload to fetch the correct URL based on the version platform and build id So all fine A special situation came up for update tests which actually use two different Firefox builds If we get the tests for the pre build how can we magically switch the tests for the target version Given that there is no easy way I decided to always use the tests from the target version and in case of UI changes we have to keep backward compatibility code in our tests and Firefox Puppeteer This is maybe the most ideal solution for us Another issue I had to solve with test packages was with release candidate builds For those builds Release Engineering is not uploading nor creating any test archive So a connection had to be made between candidate builds and CI tinderbox builds As turned out the two properties which helped here are the revision and the branch With them I at least know the changeset of the mozilla beta mozilla release and mozilla esr branches as used to trigger the release build process But sadly that s only a tag and no builds nor tests are getting created Means something more is necessary After some investigation I found out that Treeherder and its Rest API can be of help Using the known tag and walking back the parents until Treeherder reports a successful build for the given platform allowed me to retrieve the next possible revision to be used with mozdownload to retrieve the test packages json URL I know its not perfect but satisfies us enough for now Then the release promotion project as worked on by the Release Engineering team was close to be activated I heard a couple of days before that Firefox 46 0b1 will be the first candidate to get it tested on

    Original URL path: http://www.hskupin.info/2016/03/31/review-of-firefox-desktop-automation-work-q1-2016/comment-page-1/ (2016-05-01)
    Open archived version from archive

  • Suppress socket warnings when using rdiff-backup | hskupin.info
    backup sockets at all Those are bound to the current system and will be executed when an application gets started So I don t see a reason to backup those files Therefor just use the exclude sockets option for rdiff backup Please note that you will have to run rdiff backup twice before the failure message from above will no longer appear backup cron xen Post navigation Previous Post Mozmill 1 5 6 released Next Post Mozmill 1 5 8 has been released 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 3 Replies 3 Comments 0 Tweets 0 Facebook 0 Pingbacks Last reply was 1 month ago salelodenouye View July 11 2012 Hello thank you for this tip it seems to work well for my backups Reply John Damm Sørensen View 1 month ago Correct syntax is exclude sockets Reply Henrik Skupin replied View 1 month ago Thanks for letting me know That s what I already had but it was not really visible when transformed to HTML Now with the format it works Reply Photostream January 2012 M T W T F S S Oct 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 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 Automation team

    Original URL path: http://www.hskupin.info/2012/01/11/suppress-socket-warnings-when-using-rdiff-backup/comment-page-1/ (2016-05-01)
    Open archived version from archive

  • Firefox Desktop automation goals Q1 2016 | hskupin.info
    be done for Linux right now it shouldn t matter that much given that nothing in our firefox puppeteer package is platform dependent so far Expanding testing to other platforms should be trivial later on For now the primary goal is to see test results of our tests in Treeherder and letting developers know what needs to be changed if e g UI changes are causing a regression for us If you are interested in more details have a look at bug 1237550 Documentation of firefox ui tests and mozmill ci We are submitting our test results to Treeherder for a while and are pretty stable But the jobs are still listed as Tier 3 and are not taking care of by sheriffs To reach the Tier 2 level we definitely need proper documentation for our firefox ui tests and especially mozmill ci In case of test failures or build bustage the sheriffs have to know what s necessary to do Now that the dust caused by all the refactoring and moving the firefox ui tests to hg mozilla org settles a bit we want to start to work more with contributors again To allow an easy contribution I will create various project documentation which will show how to get started and how to submit patches Ultimately I want to see a quarter of contribution project for our firefox ui tests around mid this year Lets see how this goes More details about that can be found on bug 1237552 automation ci continuous integration firefox marionette QA Post navigation Previous Post Review of automation work Q4 2015 Next Post Review of Firefox desktop automation work Q1 2016 Logging In Profile cancel Sign in with Twitter Sign in with Facebook or Comment Name Email Not published Website Notify me of follow

    Original URL path: http://www.hskupin.info/2016/02/02/firefox-desktop-automation-goals-q1-2016/comment-page-1/ (2016-05-01)
    Open archived version from archive

  • Photos | hskupin.info
    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 Automation team November 23 2015 Firefox Automation report Q3 2015 October 20 2015 Crusial SSD bug and firmware fix September 28 2015 mozdownload 1 18

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