[build system] Upgrading pyarrow, builds might be temporarily broken

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[build system] Upgrading pyarrow, builds might be temporarily broken

Bryan Cutler
We are in the process of upgrading pyarrow in the testing environment, which might cause pyspark test failures until https://github.com/apache/spark/pull/26133 is merged. Apologies for the lack of notice beforehand, but I jumped the gun a little and forgot this would affect other builds too. The PR for the upgrade is all ready to go and *should* pass current tests. I'll keep an eye on it and try to get it resolved tonight. If it becomes a problem, we can try to downgrade pyarrow to where it was.

Thanks,
Bryan
Reply | Threaded
Open this post in threaded view
|

Re: [build system] Upgrading pyarrow, builds might be temporarily broken

Bryan Cutler
Update: #26133 has been merged and builds should be passing now, thanks all!

On Thu, Nov 14, 2019 at 4:12 PM Bryan Cutler <[hidden email]> wrote:
We are in the process of upgrading pyarrow in the testing environment, which might cause pyspark test failures until https://github.com/apache/spark/pull/26133 is merged. Apologies for the lack of notice beforehand, but I jumped the gun a little and forgot this would affect other builds too. The PR for the upgrade is all ready to go and *should* pass current tests. I'll keep an eye on it and try to get it resolved tonight. If it becomes a problem, we can try to downgrade pyarrow to where it was.

Thanks,
Bryan
Reply | Threaded
Open this post in threaded view
|

Re: [build system] Upgrading pyarrow, builds might be temporarily broken

Xiao Li-2
Hi, Bryan, 

Thank you for your update!

Xiao

On Thu, Nov 14, 2019 at 8:48 PM Bryan Cutler <[hidden email]> wrote:
Update: #26133 has been merged and builds should be passing now, thanks all!

On Thu, Nov 14, 2019 at 4:12 PM Bryan Cutler <[hidden email]> wrote:
We are in the process of upgrading pyarrow in the testing environment, which might cause pyspark test failures until https://github.com/apache/spark/pull/26133 is merged. Apologies for the lack of notice beforehand, but I jumped the gun a little and forgot this would affect other builds too. The PR for the upgrade is all ready to go and *should* pass current tests. I'll keep an eye on it and try to get it resolved tonight. If it becomes a problem, we can try to downgrade pyarrow to where it was.

Thanks,
Bryan


--
Databricks Summit - Watch the talks