![](https://sh.itjust.works/pictrs/image/d48ac7c9-92c1-47ae-bf39-9ee116fb736d.jpeg)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Might make a pr of some of my favorite distros. Suse would be good.
Might make a pr of some of my favorite distros. Suse would be good.
80%. Much beyond that and you get into a decreasing return on the investment of making the tests.
That’s not how a static IP works
This is horse shit
Exactly this, because there is literally fuck all any of us can do to change this. Climate change is largely the result of a couple hundred mega corporations, not the masses choosing plastic drinking straws.
Which, hey, bonus, amirite? Nothing beats a BLT with fresh, home-grown tomatoes to watch the much-quicker-than-anticipated demise of Earth.
clang bring out yer dead
Bow chicka bow wow
It’s an older crossover, but it checks out
And shitting (are we still shitting?)
good human
God, so do I. Pre-911, pre-dotcom-bubble, pre-Bush… So much to pine for in the 90s.
It could also be an issue with disk i/o, data port throughput, database performance…
I wonder if instead a log entry of some kind could be made justifying the decision, but still obviously removing the material.
Bingo, exactly this. I said 80 because that’s typically what I see our projects get to after writing actually useful tests. But if your coverage is 80% and it’s all just tests verifying that a constant is still set to whatever value, then yeah, thats a useless metric.