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

Segfault during tests for test_indirection_scalar_range_nsdfg #1421

Closed
BenWeber42 opened this issue Nov 1, 2023 · 4 comments
Closed

Segfault during tests for test_indirection_scalar_range_nsdfg #1421

BenWeber42 opened this issue Nov 1, 2023 · 4 comments
Labels

Comments

@BenWeber42
Copy link
Contributor

tests/python_frontend/indirections_test.py::test_indirection_scalar_range_nsdfg fails with a segfault for multiple PRs' test runs. This seems to be unrelated to the changes of the PRs. Currently, it looks like an issue in the test environment.

Interestingly, they only fail for Python 3.12 without simplification/optimization (3.12, 0), whereas Python 3.12 without simplification/optimization (3.7, 0) seems to succeed.

Apparently, just re-running solves the problem (#1413 (comment)).

Here is an example of such a failure: https://github.com/spcl/dace/actions/runs/6695256570/job/18190421374

@BenWeber42
Copy link
Contributor Author

Maybe we should deactivate this test until we could fix it, so PR testing stays efficient.

@phschaad phschaad added the test label Nov 1, 2023
@phschaad
Copy link
Collaborator

phschaad commented Nov 1, 2023

Maybe we should deactivate this test until we could fix it, so PR testing stays efficient.

Not sure if I'm in favor of disabling, it may lead to the test just dying out because no one bothers to fix it. This way everyone is reminded of the issue.

@BenWeber42
Copy link
Contributor Author

Maybe we should deactivate this test until we could fix it, so PR testing stays efficient.

Not sure if I'm in favor of disabling, it may lead to the test just dying out because no one bothers to fix it. This way everyone is reminded of the issue.

I agree. I meant that we disable, but clearly have someone (most likely me) assigned to it.

Seems to look better now. I think we can keep the issue open for a bit longer, but it may have resolved itself meanwhile.

@BenWeber42
Copy link
Contributor Author

We haven't seen this in a while. Closing it for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants