You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the task URL that we use on the report is not correct because the job run has not yet started on GitHub forcing us to wait and if not found using the branch URL. On those cases we should use the URL we used to use before ARROW-18028 was merged:
Raúl Cumplido / @raulcd: @kou what do you think about falling back to the previous URL if the task URL is not present because the run has not started? I am happy to work on it.
But I don't want to use the previous URL for others (Travis CI for now because we use GitHub Actions, Azure Pipelines and Travis CI in dev/tasks/tasks.yml for now).
The previous URL for Travis CI is always https://app.travis-ci.com/github/ursacomputing/crossbow/branches . We can't find the task URL from the page...
BTW, I think that the current URL isn't so bad. We can go to the task URL with 2 clicks: ✓ -> Details
See also:
As discussed on this comment:
#14446 (comment)
Sometimes the task URL that we use on the report is not correct because the job run has not yet started on GitHub forcing us to wait and if not found using the branch URL. On those cases we should use the URL we used to use before ARROW-18028 was merged:
https://issues.apache.org/jira/browse/ARROW-18028
1e481b5
On the case of GitHub:
Reporter: Raúl Cumplido / @raulcd
Original Issue Attachments:
Note: This issue was originally created as ARROW-18085. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: