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

Some reports have failed for 2023_01_01 #686

Closed
github-actions bot opened this issue Jan 28, 2023 · 6 comments
Closed

Some reports have failed for 2023_01_01 #686

github-actions bot opened this issue Jan 28, 2023 · 6 comments

Comments

@github-actions
Copy link
Contributor

Incorrect Status code 404 found for https://cdn.httparchive.org/reports/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/2023_01_01/vulnJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/drupal/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/drupal/2023_01_01/vulnJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/magento/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/magento/2023_01_01/vulnJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/wordpress/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/wordpress/2023_01_01/vulnJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top1k/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top1k/2023_01_01/vulnJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top10k/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top10k/2023_01_01/vulnJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top100k/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top100k/2023_01_01/vulnJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top1m/2023_01_01/bootupJs.json
Incorrect Status code 404 found for https://cdn.httparchive.org/reports/top1m/2023_01_01/vulnJs.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/a11yButtonName.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/drupal/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/drupal/a11yButtonName.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/magento/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/magento/a11yButtonName.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/wordpress/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/wordpress/a11yButtonName.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top1k/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top1k/a11yButtonName.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top10k/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top10k/a11yButtonName.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top100k/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top100k/a11yButtonName.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top1m/numUrls.json
2023_01_01 not found in body for https://cdn.httparchive.org/reports/top1m/a11yButtonName.json

See latest log in GitHub Actions

@tunetheweb
Copy link
Member

@rviscomi @giancarloaf any ideas what happened to httparchive.lighthouse.2022_desktop? All the rest of the tables look to be there, ready to run the reports but that one appears to be missing.

@rviscomi
Copy link
Member

Are you referring to lighthouse.2023_01_01_desktop? That appears to be there:

image

And from what I can tell of the meta dashboard, all LH tables are where they should be:

image

@tunetheweb
Copy link
Member

Wait it's not 2022 anymore :-)

Will kick off the reports now then.

@rviscomi
Copy link
Member

Any idea why the reports didn't kick off automatically, given that all the tables are there?

@tunetheweb
Copy link
Member

It's commented out in the cron. There's 5 entries:

  • # ./sync_csv.sh
  • # ./sync_csv.sh mobile
  • # ./sync_har.sh chrome
  • # ./sync_har.sh android
  • sql/generate_reports.sh ... -r "*crux*"

Only the last is uncommented. Think I checked it before and saw last one and assumed all good but that only runs the CrUX reports on the 15th of the month.

Will have a look tomorrow at scheduling one of the others to run (without doing an import). Too tired tonight!

@tunetheweb
Copy link
Member

Cron updated to and PR raised: HTTPArchive/bigquery#181

Closing this.

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

2 participants