----- Original Message ----- | From: "Camillo Bruni" <camillobr...@gmail.com> | To: "Pharo Development List" <pharo-dev@lists.pharo.org> | Sent: Sunday, July 7, 2013 5:26:45 PM | Subject: Re: [Pharo-dev] filetree jenkins job | | On 2013-07-08, at 01:59, Dale K. Henrichs | <dale.henri...@gemtalksystems.com> wrote: | > Cami, | > | > Even worse, I don't get _any_ information about failures. When I | > run unit tests headless I get the following in my output: | > | > =============================================================================== | > Notice: Errors in script loaded from | > /home/travis/dalehenrich-builderCI-3062fdf/builds/travisCI/travisCI.st | > =============================================================================== | > | > No stacks in the debug log, so I am completely blind when I run | > Pharo3.0 builds ... been happening about 2 weeks ... I assume | > there was a radical change to the way the Pharo3.0 reports | > headless errors, either by accident or on purpose... | | that's usually not a bug, it currently is a side-effect of Opal | giving proper feedback about undefined variables. | With the new classbuilder introduce we might have some side-effects | as well (there is a reported case that Martin and Christophe found). | | > Christophe will be checking into this and I am sure he'll et me | > running again ... | > | > Until I can see what's happening with the builds I can't get the | > last little bits fixed for Pharo3.0 ... very close though:) | | sometimes what helps is running in jenkins mode, failing tests | produce a serialized stack which can be drag n dropped onto an image | for easier debugging. I use that on a regular basis when figuring | out non-deterministic tests :) | | You can see such files here: | https://ci.inria.fr/pharo-contribution/job/FileTree/PHARO=30,VERSION=stable,VM=vm/ws/ |
Running on travisCI does not allow me to get access to serialized anything ... I get to see a log file (what do you expect for free:) ... a simple stack report printed is usually enough for me to figure out what's happening but the above is totally useless ... most cases reproduce locally, but the pharo3.0 issues that I'm trying to debug now are failing only on travis so I need to have something to point to what's wrong ... like I said I figured the headless operation had been jiggered in some way and will patiently wait for Christophe to come up with an acceptable solution for running on travis ... Dale
