Bcachefs Reining In Bugs: Test Dashboard Failures Drop By 40% Over Last Month

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Radtraveller
    replied
    Reining, not "Reigning"

    Leave a comment:


  • niner
    replied
    Originally posted by varikonniemi View Post
    at least it has not eaten any data yet. Fixing corner case wedging that needs extending fsck is usually expected to continue for years after being declared stable, so seeing those reduce dramatically at this point is indeed very reliability inducing.
    Can we please bury this myth?


    Version Kernel: 2620221 Tools: 7af94e14b5a9945c28a3c34e58b920e81c696a53 Description If you enable prjquota at the format time and then try to make a snapshot, you would not be able to mount the fil...


    I mean yeah, if you define "not eaten any data" as "files don't tend to magically disappear from directories -- they show up, but then you get failures trying to stat() them" then maybe yes:

    Leave a comment:


  • uid313
    replied
    Maybe he should be using Rust now since that is in the kernel?

    Leave a comment:


  • varikonniemi
    replied
    Originally posted by V1tol View Post
    Well, that looks reliable.
    at least it has not eaten any data yet. Fixing corner case wedging that needs extending fsck is usually expected to continue for years after being declared stable, so seeing those reduce dramatically at this point is indeed very reliability inducing.

    Everyone laughed at the "provocative" catchphrase but as of now it seems very possible to be the first filesystem that has never and will never eat data while being mainline.
    Last edited by varikonniemi; 01 November 2024, 07:39 AM.

    Leave a comment:


  • Mathias
    replied
    Just a little news from Drama-World:

    On Kents RC5 PR, Sasha Levin tested a tool to check how many days the patches were in linux-next (results: 5x 0 days, 21 x 2 days). That was something Linus did manually earlier and complained about. While the messages had potential to result in drama, everyone kinda tried to not directly point fingers. In the end, Kent was relieved to hear >>This is not a "shame" list but rather "look a little closer" list.​<< from Sasha. He concluded
    I've got stuff that I hold
    back for weeks (or months), and others that I'm fine with sending the
    next day, once it's passed my CI.

    I'm going to try to be better about talking about which patches have
    risks (and why that risk is justified, else I wouldn't be sending it),
    or which patches look more involved but I've got reason to be confident
    about - that can get quite subtle. That's good for everyone down the
    line in terms of knowing what to expect.​
    Linus never commented anything on this thread. Also with his complaints about Kents RC4 PR, Kent sent in the RC5 PR 6 days ahead and RC6 two days ahead of time. This is something Linus suggested as a compromise to (not) having patches in -next.

    Leave a comment:


  • V1tol
    replied
    Well, that looks reliable.

    Leave a comment:


  • Bcachefs Reining In Bugs: Test Dashboard Failures Drop By 40% Over Last Month

    Phoronix: Bcachefs Reigning In Bugs: Test Dashboard Failures Drop By 40% Over Last Month

    As part of the latest Bcachefs fixes pull request, lead developer Kent Overstreet has provided an update on the bug situation for this advanced copy-on-write open-source file-system...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
Working...
X