MozillaSecurity / MozillaSecurity/bugmon

Use stack(s) to trigger a needinfo? for bugs where we have no bisection

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
11
Forks
2
Avg merge
2h 8m
Merged PRs (30d)
1

Description

For some bugs, like TSan or ASan Nightly issues, we usually don't have a bisection (esp. for issues that have been in the codebase for a long time or where we don't have a standalone testcase but a stack.

Using this stack, it would be nice if we could automatically trigger an initial needinfo? based on the first relevant frame. The challenges here are

  1. Finding the first non-generic frame. Sometimes there are a few generic frames on top of the stack that aren't relevant. My gut feeling tells me that we can find heuristics to work around this, e.g. pick the first frame that belongs to a .c|.cpp|.rs file (not .h) that is in our codebase.

  2. If the hg annotate turns up a developer no longer working at Mozilla (which is common for old code), we might have to check the surroundings for other developers that might be able to help.

  3. We have to deal with reformat commits (I believe we have a hg ext to do this already?)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing Bugmon's existing handling of bug stacks and hg annotate, then investigate how the first relevant .c, .cpp, or .rs frame could be identified. Done would mean an agreed approach for triggering needinfo?, handling former developers through nearby ownership, and accounting for reformat commits.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cpp, python, rust
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.