access failed CI artifacts

Richard Eisenberg rae at
Thu Jan 24 18:36:59 UTC 2019

A pipeline of mine failed:

The failures are just some output changes. I could delicately use the log to extract the changes and commit them, but it would be better to have direct access to, say, the *.run.stderr files and then commit those. Is this possible? Note that I do not have a build of this tree locally, as it's the result of a rebase that affected the output. Of course, I could build locally, but it would be nice to skip that step.


More information about the ghc-devs mailing list