Good, I can wait. It's not a show-stopper for me :-) On 06/08/13 16:37, Esteban Lorenzano wrote:
ah, but in this case... probably the latest vm already fixes that :) problem is that is still not stable (the vm) so we cannot release it, but well... we'll get there soon :)
On Aug 6, 2013, at 5:36 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
you know that what is not in the bug tracker does not exists? ;)
I'm sorry, I want to take all problems into consideration, but I cannot make email archeology each time I'm going to tackle something :(
under project "Pharo VM"
thanks, and do not hesitate on asking for an account if you need it :)
Esteban
On Aug 6, 2013, at 5:17 PM, Jan Vrany <jan.vrany@fit.cvut.cz> wrote:
Hi,
here:
-------- Original Message -------- Subject: Nice VM crash Date: Fri, 21 Jun 2013 18:37:18 +0100 From: Jan Vrany <jan.vrany@fit.cvut.cz> To: Pharo Development <pharo-dev@lists.pharo.org>
Hi guys,
getting bored? Looking for an excuse to play with GDB? Here we go:
https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchma...
Okay, seriously: build 17 from Jun 17 did not crash - the Smalltalk code was the same. Jenkins executes following script:
=== export PATH=/usr/bin:$PATH
IMAGE_BASE=CalipeL-S-$BUILD_NUMBER IMAGE=$IMAGE_BASE.image
if [ ! -r Pharo.image ]; then wget -O- get.pharo.org | bash fi
./pharo Pharo.image save $IMAGE_BASE ./pharo $IMAGE config http://smalltalkhub.com/mc/JanVrany/CalipeL-S/main ConfigurationOfCalipeLS --install=0.1 ./pharo $IMAGE benchmark --json -o results.json BenchmarkMicro ===
System is running stock 32bit debian stable on VMWare ESX 5.1. I can provide more details if you like (and ask what exactly :-)
Best, Jan
And here:
-------- Original Message -------- Subject: Re: Nice VM crash - UPDATE Date: Wed, 10 Jul 2013 14:24:58 +0100 From: Jan Vrany <jan.vrany@fit.cvut.cz> To: Pharo Development <pharo-dev@lists.pharo.org>, Eliot Miranda <eliot.miranda@gmail.com>
Hi,
a small update to my VM crash. Actually, sometimes it does not crash :-) (see [1] - the VM is the same all the time). My wild guess is some GC related problem, depending on timing and actual memory contents/layout, maybe?
Cheers, Jan
[1]: https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchma...
On 06/08/13 16:12, Esteban Lorenzano wrote:
where is the report?
On Aug 6, 2013, at 4:50 PM, Jan Vrany <jan.vrany@fit.cvut.cz> wrote:
Hi Doru,
join the club:
https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchma...
I reported presumably same issue 21/06/13, update 10/07/13 :-)
Best, Jan
On 06/08/13 15:43, Tudor Girba wrote:
Hi,
It seems that the Moose build crashes the VM since yesterday evening due to a failing test. The image is based on Pharo 2.0 and is running a stable VM on Ubuntu.
See some details here: https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/804/console
The script to reproduce the problem (on Ubuntu) is:
#------------------- wget --quiet -O - http://get.pharo.org/20+vm | bash
./pharo Pharo.image save $JOB_NAME
REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main ./pharo $JOB_NAME.image config $REPO ConfigurationOfMoose --install=development ./pharo $JOB_NAME.image mooseimagesetup
./pharo $JOB_NAME.image moosetest --junit-xml-output
mv ./pharo-vm/PharoV20.sources ./ zip $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources #-------------------
Cheers, Doru
-- www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"