Add terrible script for creating list of bugs from triage metadata

[foolip]

Just to show my work. Do not review/merge.

[stephenmcgruer]

(If you delete the branch, will github eventually garbage-collect this?)

[KyleJu]

(If you delete the branch, will github eventually garbage-collect this?)

This as in this PR? No I don't think PRs ever get deleted ever unless you contact them

[KyleJu]

In terms of creating list of bugs from triage metadata, the easier way might be to use the api/metadata? API, https://wpt.fyi/api/metadata?product=safari

[foolip]

PR commit history never gets garbage collected. I suspect actually no refs ever get deleted, I once had to contact GitHub support to delete a ref.

[foolip]

Ha, https://wpt.fyi/api/metadata?product=safari definitely does most of what what I wrote code for, thanks @KyleJu! Filtering, querying Bugzilla and grouping is still needed, but I can delete some of my code. Is the status field the test results, or how can one combine the triage data with test results?

[KyleJu]

Ha, https://wpt.fyi/api/metadata?product=safari definitely does most of what what I wrote code for, thanks @KyleJu! Filtering, querying Bugzilla and grouping is still needed, but I can delete some of my code. Is the status field the test results, or how can one combine the triage data with test results?

Correct, the status field is a test result and here is the explanations for this field. In short, you should only see timeout (4) and fail (6). They should be represented in the string format, and I forgot the initial rationale behind using the enum format.

[foolip]

Aha, so it's the status from the triage data, right, not from current test results?

[KyleJu]

Aha, so it's the status from the triage data, right, not from current test results?

Correct, it's the status from the triage data. By comparing the status from the triage data and current test results, you can figure out if a metadata/URL is out-of-update