home.social

#bugpocolypse — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bugpocolypse, aggregated by home.social.

  1. Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.

    #datadive #bugtracker

  2. Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.

    #datadive #bugtracker

  3. Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.

    #datadive #bugtracker

  4. Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.

    #datadive #bugtracker

  5. Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.

    #datadive #bugtracker