You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2023/01/17 13:05:58 UTC
[GitHub] [arrow] lidavidm opened a new pull request, #33720: DO NOT MERGE: Try to reproduce wheel failures
lidavidm opened a new pull request, #33720:
URL: https://github.com/apache/arrow/pull/33720
<!--
Thanks for opening a pull request!
If this is your first pull request you can find detailed information on how
to contribute here:
* [New Contributor's Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
* [Contributing Overview](https://arrow.apache.org/docs/dev/developers/overview.html)
If this is not a [minor PR](https://github.com/apache/arrow/blob/master/CONTRIBUTING.md#Minor-Fixes). Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose
Opening GitHub issues ahead of time contributes to the [Openness](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.) of the Apache Arrow project.
Then could you also rename the pull request title in the following format?
GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
or
MINOR: [${COMPONENT}] ${SUMMARY}
In the case of PARQUET issues on JIRA the title also supports:
PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
-->
### Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes.
-->
### What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR.
-->
### Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are they covered by existing tests)?
-->
### Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `breaking-change` label.
-->
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] lidavidm closed pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
lidavidm closed pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
URL: https://github.com/apache/arrow/pull/33720
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] github-actions[bot] commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385400306
Revision: 5d2bce6f3258258cba15ff51f1ced50bef477fdc
Submitted crossbow builds: [ursacomputing/crossbow @ actions-f3e3650a1c](https://github.com/ursacomputing/crossbow/branches/all?query=actions-f3e3650a1c)
|Task|Status|
|----|------|
|wheel-manylinux2014-cp310-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939543772/jobs/6739522861)|
|wheel-manylinux2014-cp311-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939542787/jobs/6739520811)|
|wheel-manylinux2014-cp37-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939544634/jobs/6739524843)|
|wheel-manylinux2014-cp38-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939544345/jobs/6739524245)|
|wheel-manylinux2014-cp39-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939543342/jobs/6739521904)|
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] lidavidm commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
lidavidm commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385442907
@github-actions crossbow submit wheel-manylinux2014-*-amd64
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] lidavidm commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
lidavidm commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385518598
Reconstructed backtrace on #15054
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] lidavidm commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
lidavidm commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385396760
@github-actions crossbow submit wheel-manylinux2014-*-amd64
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] jorisvandenbossche commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
jorisvandenbossche commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385467615
For the faulthandler part, I tried this a while ago as well to debug some other segfault in CI, and my conclusion then was that pytest nowadays already does that by default: https://docs.pytest.org/en/7.1.x/how-to/failures.html#faulthandler
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] github-actions[bot] commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385446678
Revision: dc0137218046de795d116eccf03d5044b0f31759
Submitted crossbow builds: [ursacomputing/crossbow @ actions-89f91f1eb7](https://github.com/ursacomputing/crossbow/branches/all?query=actions-89f91f1eb7)
|Task|Status|
|----|------|
|wheel-manylinux2014-cp310-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939846256/jobs/6740186338)|
|wheel-manylinux2014-cp311-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939845028/jobs/6740183245)|
|wheel-manylinux2014-cp37-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939845175/jobs/6740183544)|
|wheel-manylinux2014-cp38-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939845704/jobs/6740184878)|
|wheel-manylinux2014-cp39-amd64|[](https://github.com/ursacomputing/crossbow/actions/runs/3939847223/jobs/6740188523)|
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] jorisvandenbossche commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
jorisvandenbossche commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385474534
Yeah, also from local development, my experience is that enabling the python faulthandler module most of the time doesn't actually result in more information being printed (at least when developing arrow, unless I am all the time using it wrongly)
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] lidavidm commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
lidavidm commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385469402
Hmm, interesting, because I don't actually see the traceback in past runs. Possibly there is no Python-side traceback then, in which case hopefully catchsegv grabs it.
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] lidavidm commented on pull request #33720: DO NOT MERGE: Try to reproduce wheel failures
Posted by GitBox <gi...@apache.org>.
lidavidm commented on PR #33720:
URL: https://github.com/apache/arrow/pull/33720#issuecomment-1385495818
Ah right, now I remember why catchsegv isn't great. We're building in release mode...
```
Backtrace:
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x17b5bb7)[0x7fed49842bb7]
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x17a1d83)[0x7fed4982ed83]
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x591c6a)[0x7fed4861ec6a]
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x16d882f)[0x7fed4976582f]
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x591c6a)[0x7fed4861ec6a]
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x12d5a94)[0x7fed49362a94]
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x591c6a)[0x7fed4861ec6a]
/lib/x86_64-linux-gnu/libc.so.6(+0x3b4d7)[0x7fed4c6c94d7]
/lib/x86_64-linux-gnu/libc.so.6(+0x3b67a)[0x7fed4c6c967a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fed4c6b1d11]
python(_start+0x2a)[0x559a27a1508a]
```
--
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: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org