On Thu, Aug 8, 2019 at 4:24 PM Antoine Pitrou wrote:
>
> Le 08/08/2019 à 16:12, Krisztián Szűcs a écrit :
> > Hi All!
> >
> > Ursabot now supports debugging failed builds with attach attaching
> > shells to the still builds right after a failing build step:
> >
> > $ ursabot project build --attac
Le 08/08/2019 à 16:12, Krisztián Szűcs a écrit :
> Hi All!
>
> Ursabot now supports debugging failed builds with attach attaching
> shells to the still builds right after a failing build step:
>
> $ ursabot project build --attach-on-failure `AMD64 Conda C++`
>
> And local source/git directorie
Hi All!
Ursabot now supports debugging failed builds with attach attaching
shells to the still builds right after a failing build step:
$ ursabot project build --attach-on-failure `AMD64 Conda C++`
And local source/git directories can also be mounted to the builder
instead of cloning arrow, this
We can now reproduce the builds locally (without the need of
the web UI) with a single command:
To demonstrate, building the master barnch and building a pull
request requires the following commands:
$ ursabot project build 'AMD64 Ubuntu 18.04 C++'
$ ursabot project build -pr 'AMD64 Ubuntu 18.0
Ok, but the configuration movement to arrow is orthogonal to
the local reproducibility feature. Could we proceed with that?
On Tue, Jul 30, 2019 at 4:38 PM Wes McKinney wrote:
> I will defer to others to investigate this matter further but I would
> really like to see a concrete and practical pa
I will defer to others to investigate this matter further but I would
really like to see a concrete and practical path to local
reproducibility before moving forward on any changes to our current
CI.
On Tue, Jul 30, 2019 at 7:38 AM Krisztián Szűcs
wrote:
>
> Fixed it and restarted a bunch of buil
Fixed it and restarted a bunch of builds.
On Tue, Jul 30, 2019 at 5:13 AM Wes McKinney wrote:
> By the way, can you please disable the Buildbot builders that are
> causing builds on master to fail? We haven't had a passing build in
> over a week. Until we reconcile the build configurations we sh
On Tue, Jul 30, 2019 at 3:23 AM Wes McKinney wrote:
> On Mon, Jul 29, 2019 at 7:58 PM Krisztián Szűcs
> wrote:
> >
> > On Tue, Jul 30, 2019 at 1:38 AM Wes McKinney
> wrote:
> >
> > > hi Krisztian,
> > >
> > > Before talking about any code donations or where to run builds, I
> > > think we first
By the way, can you please disable the Buildbot builders that are
causing builds on master to fail? We haven't had a passing build in
over a week. Until we reconcile the build configurations we shouldn't
be failing contributors' builds
On Mon, Jul 29, 2019 at 8:23 PM Wes McKinney wrote:
>
> On Mo
On Mon, Jul 29, 2019 at 7:58 PM Krisztián Szűcs
wrote:
>
> On Tue, Jul 30, 2019 at 1:38 AM Wes McKinney wrote:
>
> > hi Krisztian,
> >
> > Before talking about any code donations or where to run builds, I
> > think we first need to discuss the worrisome situation where we have
> > in some cases 3
On Tue, Jul 30, 2019 at 1:38 AM Wes McKinney wrote:
> hi Krisztian,
>
> Before talking about any code donations or where to run builds, I
> think we first need to discuss the worrisome situation where we have
> in some cases 3 (or more) CI configurations for different components
> in the project.
hi Krisztian,
Before talking about any code donations or where to run builds, I
think we first need to discuss the worrisome situation where we have
in some cases 3 (or more) CI configurations for different components
in the project.
Just taking into account out C++ build, we have:
* A config fo
Hi All,
Ursabot works pretty well so far, and the CI feedback times have become
even better* after enabling the docker volume caches, the development
and maintenance of it is still not available for the whole Arrow community.
While it wasn't straightforward I've managed to separate to source code
13 matches
Mail list logo
