Closed
Bug 1437414
Opened 7 years ago
Closed 7 years ago
Add note to docs about needing to manually process crashes for the development environment
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lonnen, Assigned: willkg)
Details
Attachments
(1 file)
I bootstrap a local dev environment with these instructions:
https://socorro.readthedocs.io/en/latest/gettingstarted.html#quickstart
I follow the additional steps in:
https://socorro.readthedocs.io/en/latest/components/webapp.html#webapp-chapter
When I load the local webapp, there are no Firefox crashes in it (supersearch, 6 months, product=Firefox).
I rerun `make dockerupdatedata` and check that it is importing stuff:
> Fetching normalization data for firefox,mobile from 2018-02-04 to 2018-02-11
> Fetching data for (firefox, ['58.0b99', '58.0', '52.6.0esr', '60.0a1', '58.0.1', '58.0.2', '59.0b8', '59.0b4', '59.0b5', '59.0b6', '59.0b7', '59.0b3'], Mac OS X)...
> 74 data points to add
> Fetching data for (firefox, ['58.0b99', '58.0', '52.6.0esr', '60.0a1', '58.0.1', '58.0.2', '59.0b8', '59.0b4', '59.0b5', '59.0b6', '59.0b7', '59.0b3'], Linux)...
> 75 data points to add
> Fetching data for (firefox, ['58.0b99', '58.0', '52.6.0esr', '60.0a1', '58.0.1', '58.0.2', '59.0b8', '59.0b4', '59.0b5', '59.0b6', '59.0b7', '59.0b3'], Windows)...
> 76 data points to add
> Fetching data for (firefox, ['58.0b99', '58.0', '52.6.0esr', '60.0a1', '58.0.1', '58.0.2', '59.0b8', '59.0b4', '59.0b5', '59.0b6', '59.0b7', '59.0b3'], Unknown)...
> 26 data points to add
> Fetching data for (FennecAndroid, ['58.0b99', '58.0', '58.0b17', '60.0a1', '58.0.1', '58.0.2', '59.0b5', '59.0b7', '59.0b3'], Linux)...
> 53 data points to add
Still no data. Is this bootstrapping postgres, es, or both?
Comment 1•7 years ago
|
||
That's expected. Processing crashes doesn't happen as part of those bootstrapping steps. Will and I have discussed processing crashes as part of the initial setup in the past and he's convinced me it's not worth adding for the amount of time/complexity it'd add.
The processor docs have a section on the various commands for pulling down and processing crashes, including an example of using them together: https://socorro.readthedocs.io/en/latest/components/processor.html#example-using-all-the-scripts
After running that, you should have crashes locally.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•7 years ago
|
||
lame. I claim you don't have a functional webapp without some crashes in there for the reports. Would we accept linking to that from the 'setup the webapp' section of the docs?
Assignee | ||
Comment 3•7 years ago
|
||
Updated•7 years ago
|
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: no crashes in dev webapp → Add note to docs about needing to manually process crashes for the development environment
Updated•7 years ago
|
Assignee: nobody → willkg
Comment 4•7 years ago
|
||
Commits pushed to master at https://github.com/mozilla-services/socorro
https://github.com/mozilla-services/socorro/commit/f41846fa83333e513b6c95876e7bd51caee0322a
fixes bug 1437414 - clarify crash data situation in getting started
This clarifies that you have a local development environment with no crash
data in it and that you need to process some crashes to add some. It also
moves the link to the processor chapter up a bit so it's clearer where those
docs are.
https://github.com/mozilla-services/socorro/commit/42e829f910f3c80c70194e8c5121f080790b05c4
Merge pull request #4335 from willkg/1437414-proc-docs
fixes bug 1437414 - clarify crash data situation in getting started
Updated•7 years ago
|
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•