-
Notifications
You must be signed in to change notification settings - Fork 4k
ARROW-15693: [Dev] Update crossbow templates to use master or main #13975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… to other repositories. 2. Modified core.py to add default_branch property and a function forchecking whether on default branch, to Target. 3. Modified template files to use the python function for checking whether on default branch. 4. Updated macros.jinja to use python function for checking whether on default branch. Co-Authored-By: Kevin Gurney <kgurney@mathworks.com>
|
These changes should be ready for review now. Our apologies for the delay - it took us some time to qualify our changes in a robust way using @lafiona's queue repository. @assignUser - if you have any bandwidth to review these changes, that would be greatly appreciated. Thank you! |
…om default_branch property of Target class. Co-authored-by: Fiona La <fionala7@gmail.com>
raulcd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @kevingurney !
There are a couple of linting issues:
/arrow/dev/archery/archery/crossbow/core.py:744:80: E501 line too long (91 > 79 characters)
/arrow/dev/archery/archery/crossbow/core.py:784:9: E266 too many leading '#' for block comment
/arrow/dev/archery/archery/crossbow/core.py:784:80: E501 line too long (109 > 79 characters)
|
I'm very sorry @raulcd - I am not sure why I didn't notice the linting issues before! Thanks for pointing them out! I'll fix them as soon as possible. |
…n from "is" to "in" after "master" is removed from the default_branch property. 2. Fix linting issues in core.py. Co-authored-by: Fiona La <fionala7@gmail.com>
|
I just pushed a fix for the linting issues. My apologies again for not noticing them sooner! |
raulcd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kevingurney ! The PR looks good to me just a comment.
2. Add missing license header text. Co-authored-by: Fiona La <fionala7@gmail.com>
raulcd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good to me. @kszucs can you take a look on this one?
kszucs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
assignUser
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks @kevingurney !
Sorry for the late review, I was out.
@kszucs I think this should be mergable now?
|
Benchmark runs are scheduled for baseline = 23c5cee and contender = 3e40cd3. 3e40cd3 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
|
['Python', 'R'] benchmarks have high level of regressions. |
|
Thanks for the code reviews everyone! Regarding the performance regressions reported by Perhaps, we should re-run the benchmarks to make sure these regressions aren't false positives. |
|
@ursabot please benchmark |
|
Benchmark runs are scheduled for baseline = 7e7b8e1 and contender = 4575b26. Results will be available as each benchmark for each run completes. |
|
Thanks for re-running the benchmarks @raulcd! I was just about to re-run them myself, but had to step away. |
|
hi @kevingurney I don't think the benchmark issues are related to this PR, I've seen this other PR reporting the same issues: |
…pache#13975) # Overview This pull request: 1. Removes hard-coded dependencies on "master" as the default branch name in the crossbow infrastructure and CI template files. # Implementation 1. Removed comment/text references to "master" branch, including URLs to other repositories. 2. Modified `core.py` to add a new `default_branch` property and a new method `is_default_branch`, for checking whether on the default branch, to the `Target` class. 3. Modified CI template files to use the new `is_default_branch` function to check whether on the default branch. # Testing 1. Using [lafiona/crossbow](https://github.com/lafiona/crossbow) as a queue repository for qualification. 2. Ran modified template jobs. All failures appeared to be unrelated to the changes. 3. The branch names for all relevant qualification jobs are prefixed with `build-34-*`. 4. Example of a passing job: [https://github.com/lafiona/crossbow/actions/runs/2920227769](https://github.com/lafiona/crossbow/actions/runs/2920227769) 5. Example of a failing job: [https://github.com/lafiona/crossbow/runs/7998190113](https://github.com/lafiona/crossbow/runs/7998190113) - in this example, the *"Push Docker Image"* workflow step is not included, since we are not on the default branch. The failure appears to be related to issues fetching R package resources and not related to the default branch checking logic. There were a variety of other kinds of failures, but none of them appear related to the default branch checking logic. # Future Directions 1. Remove "master" from `default_branch` name property of `Target` class. 2. Remove all remaining uses of "master" terminology in crossbow. 3. [ARROW-17512](https://issues.apache.org/jira/browse/ARROW-17512): Address minor issues with crossbow documentation. # Notes 1. Thank you to @lafiona for her help with this pull request! 2. Due to unexpected technical issues, we opened this pull request as a follow up to apache#13750. Please see apache#13750 for more discussion regarding qualification efforts. Lead-authored-by: Kevin Gurney <kgurney@mathworks.com> Co-authored-by: Fiona La <fionala7@gmail.com> Signed-off-by: Alessandro Molina <amol@turbogears.org>
Overview
This pull request:
Implementation
core.pyto add a newdefault_branchproperty and a new methodis_default_branch, for checking whether on the default branch, to theTargetclass.is_default_branchfunction to check whether on the default branch.Testing
build-34-*.Future Directions
default_branchname property ofTargetclass.Notes