Closed Bug 1045389 Opened 11 years ago Closed 11 years ago

Need to hide corrupted b2g datazilla data

Categories

(Data & BI Services Team :: DB: MySQL, task, P1)

x86
macOS

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jeads, Assigned: bjohnson)

References

Details

(Whiteboard: [data: data quality])

A bug in a test patch resulted in the submission of abnormally large data points to datazilla database b2g_perftest_1. I've identified the offending test runs and need the following query run to hide the data in the UI display. UPDATE `b2g_perftest_1`.`test_result` SET `status` = 2 WHERE `id` IN (296273, 296835, 298698, 301593, 301961, 303736, 304986, 305056, 306320);
Hi jeads, In production there is no table b2g_perftest_1.test_result. Please advise. mysql> show tables like 'test%'; +----------------------------------+ | Tables_in_b2g_perftest_1 (test%) | +----------------------------------+ | test | | test_aux_data | | test_collection | | test_collection_map | | test_data_all_dimensions | | test_option_values | | test_page_metric | | test_run | | test_value | +----------------------------------+ 9 rows in set (0.00 sec)
Assignee: server-ops-database → bjohnson
Whoops, that would be test_run UPDATE `b2g_perftest_1`.`test_run` SET `status` = 2 WHERE `id` IN (296273, 296835, 298698, 301593, 301961, 303736, 304986, 305056, 306320);
Done. 9 rows affected. :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Thanks for the fast turn around cyborgshadow. It looks like another corrupted data point slipped in during the interim. Could you also run? UPDATE `b2g_perftest_1`.`test_run` SET `status` = 2 WHERE `id` = 312320;
Status: RESOLVED → REOPENED
Flags: needinfo?(bjohnson)
Resolution: FIXED → ---
Done! 1 row affected. Please recheck and verify. :)
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Flags: needinfo?(bjohnson)
Resolution: --- → FIXED
Whiteboard: [ data quality ]
Whiteboard: [ data quality ] → [data: data quality]
Product: mozilla.org → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.