raulcd commented on code in PR #48583: URL: https://github.com/apache/arrow/pull/48583#discussion_r2672558856
########## .github/workflows/cuda_extra.yml: ########## @@ -0,0 +1,173 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +name: CUDA Extra + +on: + push: + branches: + - '**' + - '!dependabot/**' + paths: + - '.dockerignore' + - '.github/workflows/check_labels.yml' + - '.github/workflows/cuda_extra.yml' + - '.github/workflows/report_ci.yml' + - 'ci/docker/linux-apt-python-3.dockerfile' + - 'ci/scripts/ccache_setup.sh' + - 'ci/scripts/cpp_*' + - 'ci/scripts/install_numba.sh' + - 'cpp/src/arrow/gpu/**' + - 'compose.yaml' + - 'format/Flight.proto' + - 'python/**' Review Comment: To be honest we don't run the archery tasks on push to a branch so that seems to be more in-line to what we had in the past. I suppose the only difference is that going over all commits on main to find "the commit that broke it" won't be as easy. I've removed it to trigger on branch push and remove the PR path list so it will always check for the label. https://github.com/apache/arrow/pull/48583/changes/683247c3924714becdfd37020fcaabc44b20d9da -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
