GH-49426: [Python] Do not build pyarrow-stubs on emscripten builds#49427
GH-49426: [Python] Do not build pyarrow-stubs on emscripten builds#49427rok merged 3 commits intoapache:mainfrom
Conversation
|
|
|
@github-actions crossbow submit test-conda-python-emscripten |
|
Revision: 6b666d1 Submitted crossbow builds: ursacomputing/crossbow @ actions-e5e8b8cfe9
|
…tly fail blocking it
|
@github-actions crossbow submit test-conda-python-emscripten |
|
Revision: 3bd04d8 Submitted crossbow builds: ursacomputing/crossbow @ actions-99893ace2c
|
|
@github-actions crossbow submit test-conda-python-emscripten |
|
Revision: d5b2027 Submitted crossbow builds: ursacomputing/crossbow @ actions-50151f5e3d
|
| address = q.get(timeout=50) | ||
| time.sleep(0.1) # wait to make sure server is started | ||
| yield address | ||
| p.terminate() |
There was a problem hiding this comment.
As per claude threading.Thread.terminate doesn't exists, but this is not really an issue here.
| if is_emscripten: | ||
| # stubs are not supported in Emscripten build | ||
| return |
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit edfb24d. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
The emscripten job is currently failing due to pyarrow-stubs building.
What changes are included in this PR?
Are these changes tested?
Yes via archery.
Are there any user-facing changes?
No