Could even use GitHub Pages on top of that to render a static dashboard. On Tue, May 18, 2021 at 6:50 AM Jonathan Keane <j...@ursacomputing.com> wrote:
> Thanks for the comments + tickets Krisztián all of those sound like > good enhancements to this process. > > On the point of: > >> Error type: Internal > > I find it really useful to categorize the errors, especially if we > > have an error out of our direct reach. > > I can't think of an easy way to automate this though. > > It seems that there is a need for some extremely lightweight content > storage linked to these that could provide this kind of info. > Something like a json or yml (or almost any text format that we are > comfortable with) in the crossbow repository that someone can write > information like this and then it can be parsed and that content used > in the report so that information about external issues like this can > be kept and surfaced even if we can't automate them. > > > On Tue, May 18, 2021 at 8:16 AM Krisztián Szűcs > <szucs.kriszt...@gmail.com> wrote: > > > > Thanks Mauricio for collecting the issues! > > > > I'm placing a couple automatization ideas inline: > > > > On Tue, May 18, 2021 at 3:32 AM Mauricio Vargas > > <mauri...@ursacomputing.com> wrote: > > > > > > *NIGHTLY BUILDS REPORT* > > > > > > 2021-05-17 > > Could we send this email as a response to the original nightly report > > so we keep them organized in the same thread? > > > > > > > > > *New reported errors* > > > > > > > > > *GitHub* > > I find the report a bit hard to read due to the line breaks and > > asterisks. I think the CI service is not meaningful in the report's > > context. > > > > We could consider sending the nightly build report in both HTML and > > plaintext formats. This is not the preferred format for the dev > > mailing list but we could make an exception for the nightly reports to > > make them less noisy. Created a JIRA to track it: > > https://issues.apache.org/jira/browse/ARROW-12822 > > > > > > > > > *Build: *github-test-conda-python-3.8-spark-master > > > <https://github.com/ursacomputing/crossbow/runs/2597929901#step:7:9760 > > > > The Github statuses/checks API should return context about the build, > > optionally including the build URL (though it depends on the CI > > service integration). > > We could possibly automatize this, created a jira ticket to track it > > https://issues.apache.org/jira/browse/ARROW-12819 > > > > > > Error type: Internal > > I find it really useful to categorize the errors, especially if we > > have an error out of our direct reach. > > I can't think of an easy way to automate this though. > > > > > > Progress: No work has yet been done on this issue. > > It clearly highlights that someone should take a look at the ticket > below. > > > > > > First time issued: 2021-05-13 (4 days ago) > > Again, really useful! This is something we can automate as well, > > though we need to be careful to avoid API rate limiting. > > Created a ticket to track this: > > https://issues.apache.org/jira/browse/ARROW-12821 > > > > > > Ticket: ARROW-12817 > > We could identify streaks of failures by using a jira field (url to > > the crossbow branch perhaps), though it may not be worth the effort at > > the moment. > > > > > > > > > *Persisting errors* > > We could infer this from the first occurence of the failure based on > > https://issues.apache.org/jira/browse/ARROW-12821 > > > > The additional context you provide for the failures will help a lot to > > maintain the nightly builds, thanks again for collecting it! > > > > > > > > > *Azure* > > > > > > > > > *Build: *azure-test-r-rhub-ubuntu-gcc-release-latest > > > < > https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=5277&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=5b4cc83a-7bb0-5664-5bb1-588f7e4dc05b > > > > > > > > *Error type:* External > > > > > > *Progress**:* No work has yet been logged on this issue. > > > > > > *First time issued:* 2021-05-14 (3 days ago) > > > > > > *Ticket:* ARROW-12795 < > https://issues.apache.org/jira/browse/ARROW-12795> > > > > > > *Comment:* *I need to send a PR to R-Hub and fix bit64 installation on > the > > > Docker image.* > > > > > > > > > *Build: *azure-test-r-rstudio-r-base-3.6-opensuse42 > > > < > https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=5285&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=10284 > > > > > > > > *Error type:* External > > > > > > *Progress**:* A PR was sent to RStudio, we’ll wait for them to change > ICU > > > build in RSPM. > > > > > > *First time issued:* 2021-05-13 (4 days ago) > > > > > > *Ticket:* ARROW-12786 < > https://issues.apache.org/jira/browse/ARROW-12786> > > > > > > *Comment:* *This error shall persist until **RSPM binaries are > changed**.* > > > > > > > > > *Build:* azure-conda-osx-clang-py36-r36 > > > < > https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=5288&view=logs&j=cf796865-97b7-5cd1-be8e-6e00ce4fd8cf&t=88ee2fb8-46fd-5c68-fde3-1c8d31ba2a5f&l=1153 > > > > > > > > *Error type:* Internal > > > > > > *Progress**:* No work has yet been done on this issue. > > > > > > *First time issued:* 2021-05-13 (4 days ago) > > > > > > *Ticket:* ARROW-12782 < > https://issues.apache.org/jira/browse/ARROW-12782> > > > > > > *Related errors:** azure-conda-osx-clang-py36-r40* > > > > > > > > > *Build:* azure-test-ubuntu-20.10-docs > > > < > https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=5278&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=21906 > > > > > > > > *Error type:* External > > > > > > *Progress**:* No work has yet been done on this issue. > > > > > > *First time issued:* 2021-05-13 (4 days ago) > > > > > > *Ticket:* ARROW-12765 < > https://issues.apache.org/jira/browse/ARROW-12765> > > > > > > Comment: *This is due to a bug in the newly release sphinx 4.0 > > > <https://github.com/sphinx-doc/sphinx/issues/9210>. **Last friday the > idea > > > was to pin to** 3.5 **and* *wait for a **bug-fix release **last** > weekend. **We > > > need to wait more time and this shall go away.* > > > > > > > > > *Build: *azure-conda-win-vs2017-py36-r36 > > > < > https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=5275&view=logs&j=4c86bc1b-1091-5192-4404-c74dfaad23e7&t=92cf30d4-3662-566e-217a-149515dc97d5&l=18 > > > > > > > > *Error type:* Internal > > > > > > *Progress**:* Kristián opened PR 10322, which uses a crossbow command > to > > > support multiple arguments instead of pattern options. > > > > > > *First time issued:* 2021-05-12 (5 days ago) > > > > > > *Ticket:* ARROW-12764 < > https://issues.apache.org/jira/browse/ARROW-12764> > > > > > > *Related errors:* azure-conda-win-vs2017-py37-r40, > > > azure-conda-win-vs2017-py38, and azure-conda-win-vs2017-py39 > > > > > > *Comment:* *This error shall persist until PR 10322 is validated by the > > > team and then merged.* > > > > > > > > > *Build: *azure-test-r-linux-valgrind > > > < > https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=5289&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181 > > > > > > > > *Error type:* Internal > > > > > > *Progress**:* No work has yet been logged on this issue. > > > > > > *First time issued:* 2021-05-10 (7 days ago) > > > > > > *Ticket:* ARROW-12708 > > > > > > > > > *GitHub* > > > > > > > > > *Build: *github-test-conda-python-3.7-turbodbc-latest > > > <https://github.com/ursacomputing/crossbow/runs/2597912223#step:7:3853 > > > > > > > > *Error type:* Internal > > > > > > *Progress**:* No work has yet been done on this issue. > > > > > > *First time issued:* 2021-05-12 (5 days ago) > > > > > > *Ticket:* ARROW-12783 > > > > > > *Related errors:* github-test-conda-python-3.7-turbodbc-master > > > > > > *Comment: This error shall persist until **we fix this with a PR**.* > > > > > > > > > *Fixes* > > > > > > > > > From the errors mentioned in the report from 2021-05-14, these tickets > were > > > solved: > > > > > > - > > > > > > ARROW-12785 <https://issues.apache.org/jira/browse/ARROW-12785> - > [CI] > > > the r-devdocs build errors when brew installing gcc >
