![]() Python2 subpackages, or let us drop them for you". We (rightly) don't have the authority to say "please drop your unneeded More than we can support without upstream help. Python 2.7 will reach end of upstream support on 1st of January, 2020,Īfter almost 10 years (!) of volunteer maintenance.įedora still has more than 3000 packages depending on python2 – many Tl dr: Unless someone steps up to maintain Python 2 after 2020, we need Thanks to ROSA, Fedora, Ubuntu, Debian, Mint, openSUSE, Arch, Gentoo users and others who had made this work possible by contribution to the database! New drive models will appear at the end of the rating table and will move to the top in the case of long error-free operation. If rating is low, then look at the number of power-on days and number of errors occurred. Pay attention not only to the rating, but also to the number of checked model samples. Please be careful when reading the results table. The following formula is used to measure reliability: Power_On_Hours / (1 + Number_Of_Errors), i.e. The primary aim of the project is to find drives with longest "power on hours" and minimal number of errors. Everyone can contribute to the report by uploading probes of their computers by the hw-probe tool! ![]() The initial data (SMART reports), analysis methods and results are publicly shared in a new github repository. I've started a new project to estimate reliability of hard drives and SSD in real-life conditions based on the SMART data reports collected by Linux users in the database since 2014. Good news for all interested in hardware compatibility and reliability. To the wiki, and if you want to take the review I'll gladly take one If that's the case, please RTFM me a link Been busy lately, I'm a littleīehind on anything Fedora. The package itself is simple, but it bundles javascript and doesn'tīuild on all main platforms so I may have to be granted an exceptionįrom some group starting with an F. Support, although I have cases where it would be relevant, but I don't Overhead, but so far I've been monitoring small single-threaded I came across kcov when I was looking for a way to measure codeĬoverage in a Rust project and I'm impressed. ![]() Instead of requiring compile-time instrumentation. ![]() Lcov, except that all it needs is a binary with DWARF debuginfo It has no relation to Linux's kcov and is more akin to I just submitted a review request for kcov that I recentlyĭiscovered. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |