Skip to content
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

reduce pip verbosity in wheel builds #4651

Merged
merged 2 commits into from
Sep 27, 2024

Conversation

jameslamb
Copy link
Member

Proposes reducing the verbosity of pip wheel called in wheel builds from -vvv to -v.

This eliminates the 1000s of lines like this in CI logs:

image

to hopefully make it easier to view those logs interactively

@jameslamb jameslamb added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Sep 11, 2024
@jameslamb jameslamb requested a review from a team as a code owner September 11, 2024 16:17
@jameslamb jameslamb requested a review from AyodeAwe September 11, 2024 16:17
@github-actions github-actions bot added the ci label Sep 11, 2024
@jameslamb
Copy link
Member Author

Had to kick off another CI run because this was too old. I hope this can be merged, I think it's non-controversial and will make CI a bit easier to use.

rapids-bot bot pushed a commit to rapidsai/cudf that referenced this pull request Sep 27, 2024
Proposes some small changes I've taken as follow-ups from previous work here.

* #16745 filtered out all linter warnings about uses of `datetime.utcnow()` ... this PR limits that to only the warnings observed from `botocore` (so that the linter will helpfully warn us about such uses directly in `cudf`)
  - ref #16745 (comment)
* reduces the verbosity of logs for wheel builds (`-vvv` to `-v`)
  - similar to rapidsai/cugraph#4651

## Notes for Reviewers

This is intentionally targeted at `24.12`. No need to rush this into 24.10 before code freeze.

### How I tested this

<details><summary>locally in docker (click me)</summary>

```shell
docker run \
    --rm \
    --gpus 1 \
    -v $(pwd):/opt/work \
    -w /opt/work \
    -it rapidsai/citestwheel:latest \
    bash

pip install \
    --prefer-binary \
    'cudf-cu12[test]==24.10.*,>=0.0.0a0' \
    'flask' \
    'flask-cors' \
    'moto>=4.0.8' \
    'boto3' \
    's3fs>=2022.3.0'

cd ./python/cudf

pytest \
    cudf/tests/test_s3.py
```

</details>

Authors:
  - James Lamb (https://github.com/jameslamb)
  - Vyas Ramasubramani (https://github.com/vyasr)

Approvers:
  - Vyas Ramasubramani (https://github.com/vyasr)

URL: #16896
@jameslamb
Copy link
Member Author

/merge

@rapids-bot rapids-bot bot merged commit 54b03da into rapidsai:branch-24.10 Sep 27, 2024
132 checks passed
@jameslamb jameslamb deleted the pip-install-verbosity branch September 27, 2024 16:55
copy-pr-bot bot pushed a commit to rapidsai/cudf that referenced this pull request Sep 28, 2024
Proposes some small changes I've taken as follow-ups from previous work here.

* #16745 filtered out all linter warnings about uses of `datetime.utcnow()` ... this PR limits that to only the warnings observed from `botocore` (so that the linter will helpfully warn us about such uses directly in `cudf`)
  - ref #16745 (comment)
* reduces the verbosity of logs for wheel builds (`-vvv` to `-v`)
  - similar to rapidsai/cugraph#4651

## Notes for Reviewers

This is intentionally targeted at `24.12`. No need to rush this into 24.10 before code freeze.

### How I tested this

<details><summary>locally in docker (click me)</summary>

```shell
docker run \
    --rm \
    --gpus 1 \
    -v $(pwd):/opt/work \
    -w /opt/work \
    -it rapidsai/citestwheel:latest \
    bash

pip install \
    --prefer-binary \
    'cudf-cu12[test]==24.10.*,>=0.0.0a0' \
    'flask' \
    'flask-cors' \
    'moto>=4.0.8' \
    'boto3' \
    's3fs>=2022.3.0'

cd ./python/cudf

pytest \
    cudf/tests/test_s3.py
```

</details>

Authors:
  - James Lamb (https://github.com/jameslamb)
  - Vyas Ramasubramani (https://github.com/vyasr)

Approvers:
  - Vyas Ramasubramani (https://github.com/vyasr)

URL: #16896
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci improvement Improvement / enhancement to an existing function non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants