You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Jonathan Keane (Jira)" <ji...@apache.org> on 2021/06/11 17:27:00 UTC
[jira] [Updated] (ARROW-13060) [Dev] Process the saved nightly
build data
[ https://issues.apache.org/jira/browse/ARROW-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Keane updated ARROW-13060:
-----------------------------------
Description:
One ARROW-13059 is done and we have historical data for each build saved somewhere reliable + accessible, we can analyze it. (We can even use arrow to do that!)
At a minimum we should do the following:
* days since last passing
* last commit that passed
* % of failures in the past week, month, year
Some of this info has also been requested to be added to the emails as well, though that is a separate ticket at ARROW-12821. This ticket should be only for that information on the static site. We might use the same machinery/code for both, but they should be implemented separately so that they don't distract or block each other.
was:
One ARROW-13059 is done and we have historical data for each build saved somewhere reliable + accessible, we can analyze it. (We can even use arrow to do that!)
At a minimum we should do the following:
* days since last passing
* last commit that passed
* % of failures in the past week, month, year
> [Dev] Process the saved nightly build data
> -------------------------------------------
>
> Key: ARROW-13060
> URL: https://issues.apache.org/jira/browse/ARROW-13060
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
> Reporter: Jonathan Keane
> Priority: Major
>
> One ARROW-13059 is done and we have historical data for each build saved somewhere reliable + accessible, we can analyze it. (We can even use arrow to do that!)
> At a minimum we should do the following:
> * days since last passing
> * last commit that passed
> * % of failures in the past week, month, year
> Some of this info has also been requested to be added to the emails as well, though that is a separate ticket at ARROW-12821. This ticket should be only for that information on the static site. We might use the same machinery/code for both, but they should be implemented separately so that they don't distract or block each other.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)