shiftstack / gazelle Goto Github PK

For instance:

./cireport -job release-openshift-ocp-installer-e2e-openstack-4.4 -id 501

While prow only reports 4 failure.

Just an idea, right now it's not possible to skip jobs from a range without invoking the binary multiple times. It could be nice to let gazelle gather information for a comma-separated list of jobs, or job range specified as from-to, instead of the -from and -to flags.

Something like 1,2,5,7-9 would get jobs info for jobs 1, 2, 5, 7, 8, and 9.

Currently, all errors gathered from build log are categorized as infra failure, however this shouldn't be the case for timeouts waiting for the cluster to initialize that should instead be categorized as normal failure.

It would really be awesome if gazelle knew how to post CI results directly in gsheets without us having to copy & paste.

https://developers.google.com/sheets/api/quickstart/go

If a build fails so early it does not generate a machines.json, cireport will fail for that job ID.

When the test failure occurs during an image build (before e.g. the machines.json and openstack_nodes.log files even exist, the reported failures look like this:

Failed to get OpenStack Nodes information: Unexpected status code calling 'https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-serial-4.3/896/artifacts/e2e-openstack-serial/openstack_nodes.log': 404 Not Found
Failed to get Machines information: Unexpected status code calling 'https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-serial-4.3/896/artifacts/e2e-openstack-serial/machines.json': 404 Not Found

Even though the actual failure is:

could not copy stable-initial imagestreamtag: Timeout: request did not complete within allowed duration

Link and command to reproduce:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-serial-4.3/896

./cireport -job release-openshift-ocp-installer-e2e-openstack-serial-4.3 -id 896

The link to the build log used to be a fomula where the build ID is passed by reference. That makes copy-paste easy in Spreadsheets.

Now that the links are being assembled in Go, you can't drag the cell corner all the way up to get links to the build logs: all the links will point to the same page.

Currently, the output looks like this:

266 	2020-01-02 04:20:39 +0000 UTC 	1h49m22s 	SUCCESS ...

That means the log is not clickable and in order to make it so, one needs to do extra work in the spreadsheet. Similarly, it would be good to return the clickable links to the build-log.txt, machines.json and openstack_nodes.log files -- again, as clickable links.

To specify a cell in a TSV file needs to be interpreted as a hyperlink by the spreadsheet program (e.g. excel or google sheets), it needs the HYPERLINK formula:

=HYPERLINK("https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-openstack-4.2/266","266") 	2020-01-02 04:20:39 +0000 UTC 	1h49m22s 	SUCCESS

This will output a cell with the clickable text "266" pointing to the "https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-openstack-4.2/266" URL.

Having all the right links in there would make for a more unwieldy output (maybe we should hide it behind a switch), but it will make it much more useful for importing to a spreadsheet.