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

debugging missing build information is hard #547

Open
willkg opened this issue May 21, 2019 · 0 comments
Open

debugging missing build information is hard #547

willkg opened this issue May 21, 2019 · 0 comments

Comments

@willkg
Copy link
Contributor

willkg commented May 21, 2019

It's difficult to debug missing build information. There are multiple places where a failure results in the build information being missing from the frontend:

  1. failure in receiving the SQS message
  2. failure in reading the message or pulling the file from S3
  3. failure in adding the build information to Postgres
  4. failure in indexing into Elasticsearch

We should have easy-to-use tools to surface problems in any of these places given an S3 key or archive.mozilla.org url.

Also, it's not clear where build information came from. Was the build information captured through ingestion? Was it migrated from another source? Was it added by backfill? Fixing issue #545 might alleviate that--I don't know what that page was supposed to show.

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

No branches or pull requests

1 participant