On Aug 17, 2013, at 7:55 AM, Torsten Bergmann asta...@gmx.de wrote:
Instead of category 'setup' for #setUp and #tearDown
I would like to see 'running' since this follows the original
SUnit and tearDown has nothing to do with setting up the
test case, more with cleaning up.
I do not like
Hi,
This night, the jenkins job of Phratch failed because of an error to write the
.changes file.
Trying manually gives the same.
For information, I do not change anything in the Phratch code source.
Image
-
/Users/janniklaval/Desktop/phratchDev/phratch.image
Pharo2.0
Latest update:
On Aug 17, 2013, at 8:18 AM, jannik.laval jannik.la...@gmail.com wrote:
Hi,
This night, the jenkins job of Phratch failed because of an error to write
the .changes file.
Trying manually gives the same.
may be there is not enough space on the server.
We got from time to time issues with
Hi,
When loading stable version of pharo sound in Pharo 2.0 there is a missing
class: SoundSystem
===
This package depends on the following classes:
SoundSystem
You must resolve these dependencies before you will be able to load these
definitions:
BaseSoundSystem
===
Jannik
On Aug 17, 2013, at 8:28 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote:
On Aug 17, 2013, at 8:18 AM, jannik.laval jannik.la...@gmail.com wrote:
Hi,
This night, the jenkins job of Phratch failed because of an error to write
the .changes file.
Trying manually gives the same.
then is maybe a phratch project problem?
because I do not have that issue.
On Aug 17, 2013, at 8:32 AM, jannik.laval jannik.la...@gmail.com wrote:
On Aug 17, 2013, at 8:28 AM, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
On Aug 17, 2013, at 8:18 AM, jannik.laval
On 16 août 2013, at 21:57, Stéphane Ducasse wrote:
On Aug 16, 2013, at 3:59 PM, Camille Teruel camille.ter...@gmail.com wrote:
Also, to prevent explosion of the number of protocol names in the image, we
could agree on some naming convention.
For example, there are protocols ending
Now, without changing anything it work on my computer.
But does not work on jenkins…
It seems to break when writing files.
Probably, the issue with space as Stef propose ?
How can I avoid that ?
Jannik
On Aug 17, 2013, at 8:36 AM, Esteban Lorenzano esteba...@gmail.com wrote:
then is maybe a
I will check.
Did you check which version is marked as stable for 2.0
Hi,
When loading stable version of pharo sound in Pharo 2.0 there is a missing
class: SoundSystem
===
This package depends on the following classes:
SoundSystem
You must resolve these dependencies before you will
jannik
(ConfigurationOfPharoSound project version: '5.3') load
loads perfectly in 2.0
stable: spec
symbolicVersion: #stable
spec for: #'pharo1.0.x' version: '1.0'.
spec for: #'pharo1.1.x' version: '3.0'.
spec for: #'pharo1.2.x' version: '3.0'.
nope, the smalltalk hub diffs are clearly minor
- they are auto generate, no manual intervention needed to send them
- they are only sent if the build succeeds
- they include valuable information
- the github repository is the place where you go to find changes, it's simply
impossible to figure
I will disable it until I caught up with the current builds.
On 2013-08-17, at 15:27, Camillo Bruni camillobr...@gmail.com wrote:
nope, the smalltalk hub diffs are clearly minor
- they are auto generate, no manual intervention needed to send them
- they are only sent if the build succeeds
-
nope, the smalltalk hub diffs are clearly minor
- they are auto generate, no manual intervention needed to send them
- they are only sent if the build succeeds
- they include valuable information
like what?
- the github repository is the place where you go to find changes, it's
simply
On 2013-08-17, at 21:26, Stéphane Ducasse stephane.duca...@inria.fr wrote:
nope, the smalltalk hub diffs are clearly minor
- they are auto generate, no manual intervention needed to send them
- they are only sent if the build succeeds
- they include valuable information
like what?
I see
14 matches
Mail list logo
