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

Skip numba test that fails on ARM #14702

Merged

Conversation

brandon-b-miller
Copy link
Contributor

Nightly jobs have been failing with a numba segfault.

This appears to be a longstanding issue with numba on aarch64 fixed by numba/llvmlite#1009. Technically, the issue exists already in our tests, but it appears that changes from numba 0.58 make the conditions for the issue to occur much more likely, hence the failures occurring after removing the numba 0.58 version constraint recently. The issue should be fixed in numba 0.59.

For now however we should skip things so that nightlies can be fixed.

@brandon-b-miller brandon-b-miller added bug Something isn't working Python Affects Python cuDF API. non-breaking Non-breaking change labels Jan 3, 2024
@brandon-b-miller brandon-b-miller self-assigned this Jan 3, 2024
@brandon-b-miller brandon-b-miller requested a review from a team as a code owner January 3, 2024 20:50
python/cudf/cudf_pandas_tests/test_cudf_pandas.py Outdated Show resolved Hide resolved
@@ -1,4 +1,4 @@
# SPDX-FileCopyrightText: Copyright (c) 2023 NVIDIA CORPORATION & AFFILIATES.
# SPDX-FileCopyrightText: Copyright (c) 2023-2024, NVIDIA CORPORATION & AFFILIATES.
Copy link
Contributor

@bdice bdice Jan 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is failing style checks for a really gross reason. This is too long of a line. There's one other case where I could see this, but I don't love the solution:

# SPDX-FileCopyrightText: Copyright (c) 2021-2023, NVIDIA CORPORATION &
# AFFILIATES. All rights reserved. SPDX-License-Identifier:
# Apache-2.0

We probably need to have a discussion about what we ought to do here. I'd hate to let the line-length make this suffer from awful formatting.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can the copyright section be exempted from check somehow? It's not really a "comment" in the normal sense I'd say.

Copy link
Contributor

@bdice bdice Jan 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could # noqa but that’s even noisier and not better imo. I am inclined to say that if we require SPDX compatible license headers with all of the current wording, we have to increase the line length limits.

cc: @shwina for input

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated this to 83.

Copy link
Contributor

@bdice bdice Jan 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great. The other consideration I would raise (while hopefully avoiding bike shedding too much) is that 88 is the next most popular line length limit after 79/80. The black formatter defaults to 88. It might be wise to align with a common standard.

https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length

pyproject.toml Outdated Show resolved Hide resolved
@brandon-b-miller
Copy link
Contributor Author

/merge

@rapids-bot rapids-bot bot merged commit b83ab43 into rapidsai:branch-24.02 Jan 5, 2024
67 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working non-breaking Non-breaking change Python Affects Python cuDF API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants