Closed Bug 792869 Opened 12 years ago Closed 12 years ago

[prod] backfill for 2012-09-19

Categories

(Socorro :: Database, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: mpressman)

Details

The usual daily_matviews run failed because we're now dependent on ADU to be updated on time (post-mobeta aka v18) and it was not:

InternalError: raw_adu has not been updated for 2012-09-19

Looks like raw_adu has since been updated, so let's backfill ASAP.
Assignee: nobody → mpressman
running backfill now
backfill now finished
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Sorry, I need to reopen:

Hmm, I don't see 9/19 on https://crash-stats.mozilla.com/products/Firefox
Also not on https://crash-stats.mozilla.com/daily?p=Firefox&v[]=
I don't even see 2012-09-19 in the product_crash_ratio view in the (secondary) DB. :(
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
breakpad=# select backfill_matviews('2012-09-19');
INFO:  backfilling reports_clean
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 00:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 06:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 12:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 18:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-20 00:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-20 06:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 01:00:00 of reports_clean starting at 2012-09-20 12:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  rank_compare
INFO:  explosiveness (slow)
INFO:  correlations
 backfill_matviews 
-------------------
 t
(1 row)
FYI, I filed bug 792904 for making sure we do better with late ADU pushes in the future.
re-running as backfill_matviews('2012-09-19', '2012-09-19')
re-run of backfill complete:

breakpad=# select backfill_matviews('2012-09-19', '2012-09-19');
INFO:  backfilling reports_clean
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 00:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 06:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 12:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling 06:00:00 of reports_clean starting at 2012-09-19 18:00:00+00
CONTEXT:  SQL statement "SELECT backfill_reports_clean( first_rc, last_rc )"
PL/pgSQL function "backfill_matviews" line 51 at PERFORM
INFO:  backfilling other matviews for 2012-09-19
INFO:  adu
INFO:  signatures
INFO:  tcbs
NOTICE:  table "new_tcbs" does not exist, skipping
CONTEXT:  SQL statement "DROP TABLE IF EXISTS new_tcbs"
PL/pgSQL function "backfill_matviews" line 65 at SQL statement
INFO:  crashes by user
INFO:  home page graph
INFO:  hang report (slow)
INFO:  nightly builds
INFO:  rank_compare
INFO:  explosiveness (slow)
NOTICE:  table "crash_madu" does not exist, skipping
CONTEXT:  SQL statement "DROP TABLE IF EXISTS crash_madu"
PL/pgSQL function "backfill_explosiveness" line 4 at SQL statement
SQL statement "SELECT backfill_explosiveness(thisday)"
PL/pgSQL function "backfill_matviews" line 86 at PERFORM
NOTICE:  table "xtab_mult" does not exist, skipping
CONTEXT:  SQL statement "DROP TABLE IF EXISTS xtab_mult"
PL/pgSQL function "backfill_explosiveness" line 5 at SQL statement
SQL statement "SELECT backfill_explosiveness(thisday)"
PL/pgSQL function "backfill_matviews" line 86 at PERFORM
NOTICE:  table "crash_xtab" does not exist, skipping
CONTEXT:  SQL statement "DROP TABLE IF EXISTS crash_xtab"
PL/pgSQL function "backfill_explosiveness" line 6 at SQL statement
SQL statement "SELECT backfill_explosiveness(thisday)"
PL/pgSQL function "backfill_matviews" line 86 at PERFORM
NOTICE:  table "explosive_oneday" does not exist, skipping
CONTEXT:  SQL statement "DROP TABLE IF EXISTS explosive_oneday"
PL/pgSQL function "backfill_explosiveness" line 7 at SQL statement
SQL statement "SELECT backfill_explosiveness(thisday)"
PL/pgSQL function "backfill_matviews" line 86 at PERFORM
NOTICE:  table "explosive_threeday" does not exist, skipping
CONTEXT:  SQL statement "DROP TABLE IF EXISTS explosive_threeday"
PL/pgSQL function "backfill_explosiveness" line 8 at SQL statement
SQL statement "SELECT backfill_explosiveness(thisday)"
PL/pgSQL function "backfill_matviews" line 86 at PERFORM
INFO:  correlations
 backfill_matviews 
-------------------
 t
(1 row)
Matt,

That output looks right.  I'm wondering how you got the earlier output, where it skipped a bunch of matviews; is that the complete paste?
Josh, I ran it with only a single date, and yep, that's a complete paste
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.