The query for historical data has a hardcoded list of alerts that does not match the hardcoded list of alerts we test against. It looks like the code was not properly handling data not being in the file, and I suspect then failing the test because we assume 0s if no data. Example:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.13-e2e-azure-ovn-upgrade/1615192936746586112

This alert is not in the query and thus will never be in query_results.json file, and yet we're enforcing 0s on it.