Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[file_crash_bug] Drop the date for the first crash report #2237

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

suhaibmujahid
Copy link
Member

The date in the description is not accurate and could be confusing.

Checklist

  • Type annotations added to new functions
  • Docs added to functions touched in main classes
  • Dry-run produced the expected results
  • The to-be-announced tag added if this is worth announcing

@marco-c
Copy link
Contributor

marco-c commented Oct 5, 2023

Why isn't it accurate?

@suhaibmujahid
Copy link
Member Author

Why isn't it accurate?

It is based on the time range that we query (which is 2 months). If the crash is older, it will still say 2 months. We have a text to clarify that, but it still could be confusing more than helpful:

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature

Soccoro has an API to provide the date when the crash signature was ever seen, I'm not sure if including that date will have any value.

@marco-c
Copy link
Contributor

marco-c commented Oct 5, 2023

Soccoro has an API to provide the date when the crash signature was ever seen, I'm not sure if including that date will have any value.

Maybe you could ask some crash analysis experts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants