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".
  • mozmill | hskupin.info
    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 Q1 2015 May 12 2015 Henrik Skupin 2 Comments As you may have noticed I was not able to come up with status reports of the Firefox Automation team during the whole last quarter I feel sad about it but there was simply no time to keep up with those blog posts Even now I m not sure how often I will be able to blog So maybe I will aim to do it at least once a quarter or if possible once a month You may ask how it comes The answer is simple Our team faced some changes and finally a massive loss of core members Which means from the former 6 people only myself are remaining Since end of February all 5 former team members from Softvision are no longer participating in any of the maintained projects Thanks to all of them for the great help over all the last months and years But every project we own is now on my own shoulders And this is kinda hell of work with downsides like not being able to do as many reviews as I want for side projects One positive thing at least was that I got pulled back into the A Team at the same time With that move I m once more closer again to all the people who care about the basics of all test infrastructure at Mozilla I feel back home So what have I done the whole last quarter First it was always the ongoing daily work for maintaining our Mozmill CI system This was usually a job for a dedicated person all the last months The amount of work can sometimes eat up a whole day Especially if several regressions have been found or incompatible changes in Firefox have been landed Seeing my deliverables for Q1 it was clear that we have to cut down the time to spent on those failures As result we started to partially skip tests which were failing There was no time to get any of those fixed Happily the latest version of Mozmill is still working kinda nicely so no other work had to be dedicated for this project Most of my time during the last quarter I actually had to spent on Marionette especially building up wrapper scripts for being able to use Marionette as test framework for Firefox Desktop This was a kinda large change for us but totally important in terms of maintenance burden and sustainability The code base of Mozmill is kinda outdated and features like Electrolysis e10s will totally break it Given that a rewrite of the test framework is too cost intensive the decision has been made to transition our Mozmill tests over to Marionette Side effect was that a lot of missing features had to be implemented in Marionette to bring it at a level as what Mozmill offers Thanks for the amazing work goes to Andrew Halberstadt David Burns Jonathan Griffin and especially Chris Manchester For the new UI driven tests for Firefox Desktop we created the firefox ui tests repository at Github We decided on that name to make it clear to which product the tests belong to and also to get rid of any relationship to the underling test framework name This repository contains the harness extensions around Marionette a separate puppeteer library for back end and UI modules and last but not least the tests themselves As goal for Q1 we had to get the basics working including the full set of remote security tests and most important the update tests A lot of help on the security tests we got from Barbara Miller our intern from December to March She did great amount of work here and also assisted other community members in getting their code done Finally we got all the security tests converted My own focus beside the harness pieces were the update tests Given the complete refactoring of those Mozmill tests we were able to easily port them over to Marionette We tried to keep the class structure as is and only did enhancements where necessary Here Bob Silverberg helped with two big chunks of work which I m gladly thankful about Thanks a lot With all modules in place I finally converted the update tests and got them running for each version of Firefox down to 38 0 which will be the next ESR release and kinda important to be tested with Marionette For stability and ease of contribution we added support for Travis CI to our new repository It helps us a lot with reviews of patches from community members and they also can see immediately if changes they have done are working as expected The next big chunk of work will be to get those tests running in Mozmill CI to be renamed and the test reporting to use Treeherder Also we want to get our update tests for Firefox releases executed by the RelEng system to further reduce the amount of time for signoffs from QE About this work I will talk more in my next blog post So please stay tuned Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agendas the video recordings and notes from the Firefox Automation meetings Please note that since end of February we no longer host a meeting due to the low attendance and other meetings like the A team ones where I have to report my status automation continuous integration firefox marionette mozmill mozqa QA testing Mozilla Firefox Automation report week 51 52 2014 March 2 2015 Henrik Skupin 3 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 51 and 52 of 2014 I m sorry for this very late post but changes to our team which I will get to in my next upcoming post caught me up with lots of more work and didn t give me the time for writing status reports Highlights Henrik started work towards a Mozmill 2 1 release Therefore he had to upgrade a couple of mozbase packages first to get latest Mozmill code on master working again Once done the patch for handling parent sections in manifest files finally landed which was originally written by Andrei Eftimie and was sitting around for a while That addition allows us to use mozhttpd for serving test data via a local HTTP server Last but not least another important feature went in which let us better handle application disconnects There are still some more bugs to fix before we can actually release version 2 1 of Mozmill Given that we only have the capacity to fix the most important issues for the Mozmill test framework Henrik started to mass close existing bugs for Mozmill So only a hand full of bugs will remain open If there is something important you want to see fixed we would encourage you to start working on the appropriate bug For Mozmill CI we got the new Ubuntu 14 10 boxes up and running in our staging environment Once we can be sure they are stable enough they will also be enabled in production Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 51 and week 52 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 meeting of week 51 and week 52 automation ci firefox marionette mozmill mozqa testing Mozilla Firefox Automation report week 49 50 2014 January 22 2015 Henrik Skupin 5 Comments In this post you can find an overview about the work happened in the Firefox Automation team during week 49 and 50 Highlights During the first week of December the all hands work week happened in Portland Those were some great and inspiring days full of talks discussions and conversations about various things Given that I do not see my colleagues that often in real life I have taken this opportunity to talk to everyone who is partly or fully involved in projects of our automation team There are various big goals in front of us so clearing questions and finding the next steps to tackle ongoing problems was really important Finally we came out with a long list of todo items and more clarity about so far unclear tasks In week 50 we got some updates landed for Mozmill CI Given a regression from the blacklist landing our l10n tests haven t been executed for any locale of the Firefox Developer Edition Since the fix landed we have seen problems with access keys in nearly each locale for a new test which covers the context menu of web content Also we would like to welcome Barbara Miller in our team She joined us as an intern via the FOSS outreach program as driven by Gnome She will be with us until March and will mainly work on testdaybot and the conversion of Mozmill tests to Marionette The latter project is called m21s and details can be found on its project page Soon I will post more details about it Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 49 and week 50 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 meeting of week 48 Due to the Mozilla all hands workweek there was no meeting in week 49 automation continuous integration 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

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

  • Software | hskupin.info
    release can be seen in the changelog Thanks again to everyone who was involved in this release automation firefox Mozilla Software Mozilla Mozmill 1 5 22 and 2 0rc5 released August 28 2013 Henrik Skupin 2 Comments As of today we can announce a double release of Mozmill versions While for Mozmill 1 5 it might hopefully be the last update our final Mozmill 2 0 release is coming really close The now released RC5 should be the last release candidate Mozmill 1 5 22 Another update of Mozmill on our 1 5 branch was necessary given that the Thunderbird folks detected a memory leak bug 876399 in our module loading code via a sandbox This is now fixed and different tests no longer share global objects anymore Beside that the following improvements are also included In some cases we failed to correctly select an item from a menulist As it has been turned out a focus issue was the problem 871441 about newtab is now preloading its content and causes our waitForPageLoad method to fail when opening a new tab That only happened with Mozmill 1 5 given for Mozmill 2 0 the whole code has been rewritten 887258 At least on OS X Firefox shows a system dialog now when a test tries to enable the geolocation feature for a page To stop that from happening a new default preference has been added to Mozmill which stopped that from appearing 897891 As mentioned above it will most likely be the very last release of Mozmill 1 5 Further changes will completely go into Mozmill 2 0 which has been designed to be 100 backward compatible Mozmill 2 0rc5 It has passes a fair amount of time since our last RC4 for Mozmill has been released mid of June That was more as we have anticipated but it was worth the time In all those weeks we fixed 32 bugs for Mozmill and 4 bugs for JSBridge The most important changes are JSBridge forced single and multiple conversions of strings to unicode where it was not necessary As result sent data was not correctly transmitted or completely dismissed That was a pain given that test results were inaccurate 761603 In some cases Mozmill failed to send data during the shutdown of the application via the bridge to the Python process As result we hit an assertion and with debug builds the application crashed due to an invalid access to an object in our socket implementation via NSPR 865690 Another problem in our socket implementation was the missing handling of failed send requests Before the patch has been landed JSBridge simply ignored that and we hit a dataloss issue when too much information had to be send through the bridge 764640 Our local HTTP server based on httpd js was instantiated once for each test This caused a lot of trouble and overhead Now it is created on startup of the application and keeps running until shutdown With that you will also be able to use it while Mozmill is in manual mode 881657 Various changes to the restart logic have been included With that we also got our state machine implemented for restart tests 895657 Specifically for Metro Firefox we landed support for new touch events 880426 Full details about the underlying changes in RC5 can be found in the changelog for Mozmill 2 0rc5 and JSBridge 3 0rc5 automation firefox mozmill Software testing Mozilla MozInstall 1 0 released June 11 2012 Henrik Skupin Leave a comment A crucial part of test automation is the fact that you can install and uninstall the application under test While the installer part for Gecko based applications was already included in MozInstall we missed the uninstaller feature I have added this feature now for the 1 0 release On Windows it will first try to run the Firefox uninstaller in silent mode to remove any trace even from the registry If files remain or if you are on another platform the specified folder will just be wiped out This work is part of our overall code rewrite of the Mozmill Automation scripts for Mozmill 2 0 whereby a lot of useful code will be merged with existing mozbase packages or new packages like the mozdownload one will be created Keep in mind that this release changes the API of several functions We are aware of that and hope that everyone of you will be able to adapt to it easily It was necessary before more and more projects rely on this package For any details please see the appropriate README file Otherwise here some examples CLI cd Volumes mozilla builds mozinstall firefox 13 0 en US dmg Volumes mozilla builds FirefoxAurora app Contents MacOS firefox mozuninstall firefox With those two commands the specified DMG image of Firefox 13 will be installed into a sub folder of the current working directory and removed right after The installer will print the location of the actual binary to stdout API import mozinstall path mozinstall install firefox 13 0 en US exe print mozinstall get binary path firefox mozinstall uninstall path This code is the equivalent to the CLI example above It installs Firefox into a sub folder of the current working directory and returns the path With the call to get binary and by specifying the type of application the actual binary will be returned Replace firefox with thunderbird if you want to install a Thunderbird build Finally the uninstaller expects the path Firefox has been installed into and removes the application automation firefox mozbase Software testing Mozilla Software Mozmill 1 5 12 released May 7 2012 Henrik Skupin 2 Comments Something we have learned over the weekend was Never say never After we have released the 1 5 11 release of Mozmill on April 19th we were sure to not have to ship any other release off this branch We want to concentrate our work on Mozmill 2 0 and get it out as

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

  • Software | hskupin.info
    expect by default in sub modules Bug 970820 Mozmill aborts with socket timeout when trying to send the report Changes in 2 0 8 Bug 1067939 JSBridge and Mozmill broken due to let changes in bug 1001090 Please keep in mind that Mozmill 2 0 does not support electrolysis e10s builds of Firefox yet We are working hard to get full support for e10s added and hope it will be done until the next version bump mid of October Thanks everyone who was helping with those releases automation firefox mozmill mozqa Mozilla Software Mozdownload 1 10 released November 19 2013 Henrik Skupin 1 Comment As of now we have released a new version of mozdownload The 1 10 release contains a couple of new features bug fixes and absolutely to mention a suite of tests A big thank you goes here to Johannes and Jarek Both spend a lot of time again to make it a successful and lesser bug prone release Here some major items to highlight Addition of tests for all types of scrapers and a lot for command line options Output of all candidate builds founds if build number has been specified Add support for tinderbox stub installer Allow to download files with different extensions than exe A full list of features can be found in the changelog firefox mozdownload Mozilla Software Mozmill 1 5 12 released May 7 2012 Henrik Skupin 2 Comments Something we have learned over the weekend was Never say never After we have released the 1 5 11 release of Mozmill on April 19th we were sure to not have to ship any other release off this branch We want to concentrate our work on Mozmill 2 0 and get it out as soon as possible But things can change and sometimes faster as expected So by last Friday it was already late in the evening Mike Conley contacted me on IRC and mentioned that Mozmill will be broken starting with tomorrows build The reason for it was the Global Per Compartment patch which has been landed in Nightly builds of Firefox and Thunderbird at that time Great Why do things like those happen just before when I m already in my weekend Anyway given the importance of this bug it broke the whole test infrastructure of Thunderbird which mostly relies on Mozmill I was talking immediately to Clint Talbert Given the good bug report from John Schoenick we were directly aware of what the problem was and agreed on a new API to get the issue fixed So I have spent a good portion of my Saturday and Sunday evening to put together a patch which removed the broken code in waitForPageLoad and replaces it with the new API So by now we do no longer add a custom mozmillDocumentLoaded property to all windows but have a nice windowMap object that handles all the loaded states of each window on its own I think that s great and modifying the DOM of each window was even a bad idea since the beginning of the project Good to see that killed That means early today we got all patches landed and I was able to release Mozmill 1 5 12 to PyPI and even the uploaded extension on addons mozilla org has been approved in the meantime If you haven t updated yet and you make use of Nightly builds you should do it now Lets cross the fingers that no other unexpected issues will arise and force another 1 5 branch release firefox mozmill mozqa Software testing Mozilla Software Nightly Tester Tools 3 3 released May 3 2012 Henrik Skupin Leave a comment Having a good experience when testing Firefox Nightly builds should be self evident Therefor the QA Automation Services team is maintaining the Nightly Tester Tools extension which brings a couple of useful features to ease the testing efforts While the extension works fine most of the time we unfortunately fail at times when a version bump for Firefox happens Exactly this action repeats in a 6 week interval and is the release cycle of Firefox So what happens here The extension registers binary components for the crashme feature in the manifest file and that s why it is not handled as a compatible by default extension by the add ons manager So right after a version bump the extension gets marked as incompatible until the compatibility information on addons mozilla org has been updated This results in an unavailability of the extension in Nightly builds for a couple of hours or even a day depending on when one of us has time to actually do the version bump That had to be changed and thankfully Szabolcs Hubai has spent some time on it to fix the problem and to make our extension compatible by default From now on you will never see the Nightly Tester Tools disabled after a version bump of Firefox which is great I hope you all will enjoy it With the 3 3 release we also ship some other fixes which you can read about in the changelog You want to help in the development of the extension Feel free to contact us as usual via MozIRC or our mailing list addons extension firefox mozqa testing Mozilla Software MemChaser 0 2 released March 2 2012 Henrik Skupin 4 Comments Exactly one month after we have released our initial version of MemChaser version 0 2 has been made publicly available You can install the add on as usual from addons mozilla org or if it is already installed simply check for updates within the Add ons Manager A couple of subtle changes have been made which will give a better experience for users So we have combined the formerly two widgets in the Add on bar into a single one to prevent other extensions from inserting their widgets in between At the same time the width has been reduced to not waste too much space

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

  • Crusial SSD bug and firmware fix | hskupin.info
    If I had no other machine available a reboot of my laptop was necessary due no keyboard press was accepted All this came to a final end by last Friday when I wanted to participate in a debugging theme night in the local CCC chaos computer club hacker space Once arrived there I wanted to boot up my laptop but I haven t seen more than a black screen after the initial BIOS routines were done It didn t went away after a couple of cold restarts So actively participating was only a dream Also the first question Looks like your SSD died How is your 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

    Original URL path: http://www.hskupin.info/2015/09/28/crusial-ssd-bug-and-firmware-fix/ (2016-05-01)
    Open archived version from archive

  • firmware | hskupin.info
    was that in some irregular intervals my LightDM display manager froze and needed a restart by logging into my machine via SSH from a different machine If I had no other machine available a reboot of my laptop was necessary due no keyboard press was accepted All this came to a final end by last Friday when I wanted to participate in a debugging theme night in the local CCC chaos computer club hacker space Once arrived there I wanted to boot up my laptop but I haven t seen more than a black screen after the initial BIOS routines were done It didn t went away after a couple of cold restarts So actively participating was only a dream Also the first question Looks like your SSD died How is your 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

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

  • SSD | hskupin.info
    was that in some irregular intervals my LightDM display manager froze and needed a restart by logging into my machine via SSH from a different machine If I had no other machine available a reboot of my laptop was necessary due no keyboard press was accepted All this came to a final end by last Friday when I wanted to participate in a debugging theme night in the local CCC chaos computer club hacker space Once arrived there I wanted to boot up my laptop but I haven t seen more than a black screen after the initial BIOS routines were done It didn t went away after a couple of cold restarts So actively participating was only a dream Also the first question Looks like your SSD died How is your 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

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

  • mozdownload 1.18 released | hskupin.info
    print scraper filename Hereby the factory class is smart enough to only select those passed in options which are appropriate for the type of scraper If you have to download different types of builds you will enjoy that feature given that only the scraper type has to be changed and all other options could be still passed in We hope that this new feature will help you by integrating mozdownload into your own project There is no need anymore by using its command line interface through a subprocess call The complete changelog can be found here automation firefox mozdownload QA Software Post navigation Previous Post Firefox Automation report Q2 2015 Next Post Crusial SSD bug and firmware fix 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 4 Replies 0 Comments 4 Tweets 0 Facebook 0 Pingbacks Last reply was 7 months ago Planet Ateam View 7 months ago Henrik Skupin mozdownload 1 18 released http t co ok2ynpeWCz Reply EdgarsLabRat View 7 months ago moz Henrik Skupin mozdownload 1 18 released http t co Of7IL2V0Bj Reply planetmozilla View 7 months ago Henrik Skupin mozdownload 1 18 released http t co zWt7BDJNuR Reply PlanetFeeds View 7 months ago Henrik Skupin mozdownload 1 18 released Today we have released mozdownload 1 18 to PyPI The reason why I th http t co HH21QIyGNR Reply Photostream September 2015 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

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

  • mozdownload | hskupin.info
    Sadly we noticed another problem during restarts of the application on OS X bug 966234 which forced us to fix mozrunner Henrik released mozrunner 5 34 which includes a fix how mozrunner retrieves the state of the application during a restart It was failing here by telling us that the application has quit while it was still running As result Mozmill started a new Firefox process which was not able to access the still used profile A follow up Mozmill release was necessary so we went for testing it As another great highlight for community members who are usually not able to attend our Firefox Automation meetings we have started to record our meetings now So if you want to replay the meetings please check our archive Individual Updates For more granular updates of each individual team member please visit our weekly team etherpad for week 5 and week 6 Meeting Details If you are interested in further details and discussions you might also want to have a look at the meeting agenda and notes from the Firefox Automation meetings of week 5 and week 6 automation ci firefox firefox automation mozdownload mozmill Mozilla Software Mozdownload 1 10 released November 19 2013 Henrik Skupin 1 Comment As of now we have released a new version of mozdownload The 1 10 release contains a couple of new features bug fixes and absolutely to mention a suite of tests A big thank you goes here to Johannes and Jarek Both spend a lot of time again to make it a successful and lesser bug prone release Here some major items to highlight Addition of tests for all types of scrapers and a lot for command line options Output of all candidate builds founds if build number has been specified Add support for tinderbox stub installer Allow to download files with different extensions than exe A full list of features can be found in the changelog firefox mozdownload Mozilla Automation Development report week 34 2013 August 26 2013 Henrik Skupin 3 Comments Last week was a really productive week when we look over the accomplished tasks Across different test frameworks and tools we got a lot done Especially the mozdownload project raises interests by even more people who want to help with their own contribution Thank you all who were involved Highlights To appreciate all the hard work done by Johannes Vogel on the mozdownload project we promoted him to the reviewer status With this recognition he is now able to help us driving this project forward with a faster pace by doing code reviews A delicacy was also his patch for getting the long outstanding test infrastructure working for mozdownload It landed last week and gave Dave Hunt the opportunity to get Travis CI support added Over the past couple of Firefox branch merges we experienced troubles with our Mozmill tests execution within mozmill ci This was caused by a bug in one of the plugins in use which only checks the

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