How does that work?

I am interested in the Postgres thing.

Phil





On Mon, Feb 10, 2014 at 11:59 AM, Guillermo Polito <guillermopolito@gmail.com> wrote:
Well, I managed to figure out why the linux slave was not working: the amount of workers went magically to 0... The windows one is offline such as the ones in pharo's ci server, because of some connection issue, probably cloudstack issue).

So pharo20 is green as expected for mysql-linux. Pharo3 is red because of the layout error.

I just added postgres, which has failing tests because the database is not created :).


Of course if somebody wants to help (configuring one database engine, adding tests, etc), do not hesitate :).

Guille


On Mon, Feb 10, 2014 at 11:42 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
Any news on this?

I would love to test DBs on Pharo 3.0 :)

Doru



On Fri, Feb 7, 2014 at 11:44 AM, Guillermo Polito <guillermopolito@gmail.com> wrote:

The slaves are dead. I will talk with christophe as soon as i arrive to the office :)

Le 7 f�vr. 2014 05:42, "Tudor Girba" <tudor@tudorgirba.com> a �crit :

It seems that the jobs do not manage to finish :(

Doru


On Thu, Feb 6, 2014 at 1:47 PM, Guillermo Polito <guillermopolito@gmail.com> wrote:
The ci jobs :). I didn't want to announce them (and actually i didn't do it properly) until having them finished at some good degree.

The ci jobs for dbxtalk will give the people doing dbxtalk so muuuuch air (no more manual testing on 3 platforms x 5+ different database engines per change).
� + binaries available and built every day
�



On Thu, Feb 6, 2014 at 1:34 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
What was a bit secret?

Doru


On Thu, Feb 6, 2014 at 12:25 PM, Guillermo Polito <guillermopolito@gmail.com> wrote:
Well, it was a bit secret, but I was starting on my free time to setup some ci jobs to build automagically all the opendbx libraries + test them.


Now my problem is that my free time for hacking on non phd stuff -> 0 lately... :/


On Thu, Feb 6, 2014 at 12:13 PM, Torsten Bergmann <astares@gmx.de> wrote:
And Sven insist on still cutting/copying/evaluating one-liners
in the age of a configuration browser where loading is just mouse
clicking ;)

But putting jokes aside - it would IMHO be really important to
have DBXTalk running for Pharo 3.0. Without good database
support one would loose any argument for Pharo in the
business world...

It would also be a real bonus if the necessary support DLL's/shared libs
could be easily provided or installed.

For instance the PUnQLite (Pharo wrapper for UnQlite NoSQL) provides
the current binaries on Github https://github.com/mumez/PunQLite

Or the NaCl (a binding for Crypto-Nacl library) directly downloads
and installs them when you install the config (see ConfigurationOfNacl in
config browser of Pharo 3.0).

Easy access without much hazzle is always a plus... install, connect to
the DB and go!

Thx
T.

> Gesendet: Donnerstag, 06. Februar 2014 um 11:54 Uhr
> Von: "Sven Van Caekenberghe" <sven@stfx.eu>
> An: "Pharo Development List" <pharo-dev@lists.pharo.org>
> Cc: dbxtalk@googlegroups.com
> Betreff: Re: [Pharo-dev] Fwd: working on pharo 3.0?
>
> Ah, it is just because you insist on using old school two line code ;-)
>
> On 06 Feb 2014, at 11:38, Tudor Girba <tudor@tudorgirba.com> wrote:
>
> > Gofer new
> > � � smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver';
> > � � package: 'ConfigurationOfOpenDBXDriver';
> > � � load
> > #ConfigurationOfOpenDBXDriver asClass loadBleedingEdge
> >
>
> Gofer new
> � smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver';
> � configurationOf: 'OpenDBXDriver';
> � loadVersion: #bleedingEdge.
>
> Just joking,
>
> Sven
>
>





--

"Every thing has its own flow"




--

"Every thing has its own flow"



--

"Every thing has its own flow"