Closed
Bug 1054452
Opened 10 years ago
Closed 10 years ago
Datazilla Repository Update
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task, P1)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jeads, Assigned: cturra)
References
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/767] )
Attachments
(1 file)
91.13 KB,
application/x-gzip
|
Details |
A new datazilla repository is ready to push to stage. One of the main things included in this release is fix for a data corruption issue resulting from overloading the device type with memory information in a single property in the json sent to datazilla. This release requires running a specialized manage.py command to reset some corrupted machine/test relationships. Once the repository is updated on stage, please run the following manage.py commands: python manage.py fix_b2g_machines --project b2g --min_id 354404 >b2g_fix_out.txt python manage.py fix_b2g_machines --project b2gtw --min_id 354404 >b2gtw_fix_out.txt Note: fix_b2g_machines runs an ALTER statement modifying the UNIQUE index on the b2g_perftest_1.machine and b2gtw_perftest_1.machine tables so the user running the command will need to have sufficient DB privileges. The first command will run for awhile, the second will be quick. If everything goes as planned we won't need the output files but if something goes wrong, they will give me some ideas as to what is going on. This release includes the following changes: 1.) Addresses Bug 1046056, Bug 1050179, and Bug 1047324 The manage.py command fix_b2g_machines iterates through raw json objects stored in b2g_perftest_1/b2gtw_perftest_1 and builds an index in memory using the machine name (mac address), operating system id, and device type as a unique key. It then compares this index to the one in the machine table, inserting missing combinations, and reusing the correct ones that have been inserted to re-associate the correct machine_id to the corresponding test_run.id using the new version of the machine table. 2.) Addresses Bug 1007774 Adds a target line to the main graph for device/test combination listed in https://github.com/mozilla-b2g/gaia/blob/master/tests/performance/config.json#L14. This is done dynamically by ingesting the config.json file and matching device/test names. 3.) Addresses Bug 1011577 Application load defaults are now set to: Test: startup_>_moz-app-visually-complete Time Range: 7 Days Gaia Branch: master Device: flame-319MB 4.) Addresses Bug 1047306 Added ingestion alerts for flame-319MB.
Assignee | ||
Comment 1•10 years ago
|
||
i have updated stage from the repo and attached you will find the output from both these manage.py commands.
Reporter | ||
Comment 2•10 years ago
|
||
Looks good! The manage command looks like it resolved the data integrity issue. Please push this to production, there may be some follow up changes next week but we can address those in a different bug. Thanks for the quick turn around.
Assignee | ||
Comment 3•10 years ago
|
||
great! i have gone ahead and pushed these changes out to prod as requested and will mark this bug as r/fixed.
Status: NEW → RESOLVED
Closed: 10 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•