And here I wrote what we are doing so that others know :)
http://marianopeck.wordpress.com/2012/07/25/reviving-ci-test-failures-in-local-machine/
Thanks Cami and Sean. You rock.
Cheers,
On Wed, Jul 25, 2012 at 6:45 AM, Camillo Bruni camillobr...@gmail.comwrote:
On 2012-07-25, at 00:50, Sean
On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni camillobr...@gmail.comwrote:
From now on all the test-failures are serialized on the build server.
This allows us to quickly find the cause of a failing test:
- download the .fuel file for the failing test
- materialize the .fuel in the image
On 2012-07-24, at 16:29, Mariano Martinez Peck wrote:
On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni camillobr...@gmail.comwrote:
From now on all the test-failures are serialized on the build server.
This allows us to quickly find the cause of a failing test:
- download the .fuel file
On Tue, Jul 24, 2012 at 4:35 PM, Camillo Bruni camillobr...@gmail.comwrote:
On 2012-07-24, at 16:29, Mariano Martinez Peck wrote:
On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni camillobr...@gmail.com
wrote:
From now on all the test-failures are serialized on the build server.
This
THere is something I don't understand. If I see:
https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/pharo-2.0-tests/Architecture=32,OS=mac/ws/Pharo-2.0-AfterRunningTests/
it seems it is independent of a particular build. What does it mean? that
we only have the .fuel of the last build? if this
Mariano Martinez Peck wrote
we only have the .fuel of the last build?
Why don't we zip any fuel files for failing tests in the artifact. This way,
anyone can download and reconstruct the system. Also, the workspace is only
available when we are logged in.
Cheers,
Sean
--
View this message
On Tue, Jul 24, 2012 at 10:09 PM, Sean P. DeNigris s...@clipperadams.comwrote:
Mariano Martinez Peck wrote
we only have the .fuel of the last build?
Why don't we zip any fuel files for failing tests in the artifact.
I don't know much about Jenkins, but if that allows me to have the
Mariano Martinez Peck wrote
but if that allows me to have the .fuel
files for each version, then please go ahead :)
The zip artifact now includes all the fuel files. I didn't add the fuel
files as separate artifacts because it seems there's no way to specify a
target folder for artifacts
On 2012-07-25, at 00:50, Sean P. DeNigris wrote:
Mariano Martinez Peck wrote
but if that allows me to have the .fuel
files for each version, then please go ahead :)
The zip artifact now includes all the fuel files. I didn't add the fuel
files as separate artifacts because it seems
On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni camillobr...@gmail.comwrote:
From now on all the test-failures are serialized on the build server.
This allows us to quickly find the cause of a failing test:
- download the .fuel file for the failing test
Where can I find these .fuel of the
in the Workspace of the job
-- Pavel
On Mon, Jul 23, 2012 at 10:22 AM, Mariano Martinez Peck
marianop...@gmail.com wrote:
On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni camillobr...@gmail.com
wrote:
From now on all the test-failures are serialized on the build server.
This allows us to
On Sun, Jul 22, 2012 at 11:11 AM, Marcus Denker marcus.den...@inria.frwrote:
On Jul 22, 2012, at 10:00 AM, Stéphane Ducasse wrote:
I love that scenario :)
This is great that powerful tools let us imagine and build solutions
that would not be possible
before. Power to imagination…
And
I love that scenario :)
This is great that powerful tools let us imagine and build solutions that would
not be possible
before. Power to imagination…
It fits perfectly with one of the motto of Pharo: Inventing the future.
On Jul 20, 2012, at 6:09 PM, Camillo Bruni wrote:
From now on all the
On Jul 22, 2012, at 10:00 AM, Stéphane Ducasse wrote:
I love that scenario :)
This is great that powerful tools let us imagine and build solutions that
would not be possible
before. Power to imagination…
And it is an example for a building block that helps to build things. Things
that
nice explanation. Indeed I really liked IS but fuel is the way to go :)
On Jul 22, 2012, at 11:11 AM, Marcus Denker wrote:
On Jul 22, 2012, at 10:00 AM, Stéphane Ducasse wrote:
I love that scenario :)
This is great that powerful tools let us imagine and build solutions that
would not be
Wow! This is truly science fiction.
Cheers,
Doru
On 20 Jul 2012, at 18:09, Camillo Bruni wrote:
From now on all the test-failures are serialized on the build server.
This allows us to quickly find the cause of a failing test:
- download the .fuel file for the failing test
- materialize
On Sat, Jul 21, 2012 at 3:29 PM, Tudor Girba tu...@tudorgirba.com wrote:
Wow! This is truly science fiction.
hehehe yes, but there are still some problems when serializing
contexs/debuggers. I would like to clarify the possible problems.
When you serialize a context, we serialize all the
From now on all the test-failures are serialized on the build server.
This allows us to quickly find the cause of a failing test:
- download the .fuel file for the failing test
- materialize the .fuel in the image and debug the code
| aContext |
aContext := FLMaterializer
18 matches
Mail list logo
