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".
  • Survey about sharing information inside the Firefox Automation team | hskupin.info
    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 Post a Reply to PlanetFeeds 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

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


  • October | 2015 | hskupin.info
    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

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

  • 23 | November | 2015 | hskupin.info
    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 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 Automation team November 23 2015

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

  • Firefox in your country | hskupin.info
    Notify me of new posts by email 4 Replies 4 Comments 0 Tweets 0 Facebook 0 Pingbacks Last reply was September 22 2008 MauricioC View September 21 2008 You mean Brazil Brasilia is a city not a country Reply Henrik Skupin View September 21 2008 Yes indeed Thanks for mentioning that Reply Smigs View September 22 2008 You mean the United Kingdom I suppose England is a country but surely the survey must be targeting Scotland Wales Northern Ireland too Reply Henrik Skupin View September 22 2008 Sure It s corrected Looks like a darn posting But nice to see how many people are interested at least to read about the survey Reply Photostream September 2008 M T W T F S S Aug Oct 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

    Original URL path: http://www.hskupin.info/2008/09/21/firefox-in-your-country/ (2016-05-01)
    Open archived version from archive

  • Firefox Automation report – Q3 2015 | hskupin.info
    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 Post a Reply to Planet Ateam 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

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

  • Firefox Automation report – Q3 2015 | hskupin.info
    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 Post a Reply to PlanetFeeds 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

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

  • September | 2015 | hskupin.info
    backup doing which I actually got from different people was kinda expected Thankfully I was able to answer that it is only 2 days old But even with this a lot of work would be ahead of me Anyway I will have to think about if I wanna go back there after that bad omen Being back at home and having the machine turned off for a while it actually booted again Hurray I was confronted with all the orphaned nodes again across the partitions which I had to repair first but then the system started up as usual After creating another backup I did some more investigations to see if the hard drive is reporting any kind of failure But all looked fine as before All entries of the smart status didn t show any failure So I did a long test with smartctl and once I got the full report I saw a line which told that my SSD might be affected by a firmware bug which let it stop working until the the next reboot And during a reboot even a BSOD could happen The problem will start to occur after the first 5000 hours on time usage and will will continue to happen even with a drive reset A full description can be found at tomshardware website After reading the details and the announcements from Crucial about this problem I look at the firmware of my SSD drive and noticed that it is years old It s version was 000F which looks to be the second version of the firmware of this drive Since then numerous updates have been released So it was clear to me that an update of the firmware was necessary I finally did that with a bootable CD R and all went smoothly The necessary restart didn t show a problem and even I was confronted with orphaned nodes most likely from the last shutdown the system works perfectly I did various tests for all those situations which caused my machine to fail in the past All of them passed No more hanging videos while walking around and also no read only remounted file systems after taking the machine out of the docking station or putting it back into Also no freeze of LightDM has been seen so far I for myself will learn from it and will check for firmware updates way more often Also including the hard drive now One more thing you might wanna do if you own a SSD and run Linux is to update several mounting parameters to extend your disk lifetime firmware SSD Mozilla mozdownload 1 18 released September 14 2015 Henrik Skupin 4 Comments Today we have released mozdownload 1 18 to PyPI The reason why I think it s worth a blog post is that with this version we finally added support for a sane API With it available using the mozdownload code in your own script is getting much easier So there is

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

  • 20 | October | 2015 | hskupin.info
    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

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