Vm-dev April 2018

vm-dev@lists.squeakfoundation.org

43 participants
235 discussions

Errored: OpenSmalltalk/opensmalltalk-vm#1236 (Cog - 4c4686e)
by Travis CI 01 Apr '18

01 Apr '18

Build Update for OpenSmalltalk/opensmalltalk-vm ------------------------------------- Build: #1236 Status: Errored Duration: 16 minutes and 31 seconds Commit: 4c4686e (Cog) Author: Fabio Niephaus Message: Skip SUnit testing in Sista builds View the changeset: https://github.com/OpenSmalltalk/opensmalltalk-vm/compare/79c0809998d5...4c… View the full build log and details: https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/360911482?utm_s… -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications This email was sent to vm-dev(a)lists.squeakfoundation.org (mailto:vm-dev@lists.squeakfoundation.org) unsubscribe from this list (http://clicks.travis-ci.com/track/unsub.php?u=14313403&id=e17cae7852394d919…)

1 0

Build failed: opensmalltalk-vm 1.0.1206
by AppVeyor 01 Apr '18

01 Apr '18

1 0

Re: [Vm-dev] [OpenSmalltalk/opensmalltalk-vm] Skip SUnit testing in Sista builds (4c4686e)
by Fabio Niephaus 01 Apr '18

01 Apr '18

@clementbera I am not sure if SUnit tests should run on Sista VMs as part of our CI infrastructure. Currently, it fails because the script is unable to locate VM binaries ([example](https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/36054314…). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/4c4686e18373639502…

1 0

[OpenSmalltalk/opensmalltalk-vm] 4c4686: Skip SUnit testing in Sista builds
by GitHub 01 Apr '18

01 Apr '18

Branch: refs/heads/Cog Home: https://github.com/OpenSmalltalk/opensmalltalk-vm Commit: 4c4686e183736395021654c29b0fe995384e5449 https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/4c4686e18373639502… Author: Fabio Niephaus <code(a)fniephaus.com> Date: 2018-04-01 (Sun, 01 Apr 2018) Changed paths: M tests/smalltalkCI.sh Log Message: ----------- Skip SUnit testing in Sista builds

1 0

Re: [Vm-dev] [Pharo-dev] Image crashing on startup, apparently during GC
by Esteban Lorenzano 01 Apr '18

01 Apr '18

hi, > On 24 Mar 2018, at 09:50, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 23/03/2018 à 21:52, Eliot Miranda a écrit : >> Hi Damien, >> >> Indeed the image is corrupt at start-up. See below. >> >> >> Right. This VM is prior to the bug fixes in VMMaker.oscog-eem.2320: >> >> Spur: >> Fix a bad bug in SpurPlnningCompactor. >> unmarkObjectsFromFirstFreeObject, used when the compactor requires more >> than one pass due to insufficient savedFirstFieldsSpace, expects the >> corpse of a moved object to be unmarked, but >> copyAndUnmarkObject:to:bytes:firstField: only unmarked the target. >> Unmarking the corpse before the copy unmarks both. This fixes a crash >> with ReleaseBuilder class>>saveAsNewRelease when non-use of cacheDuring: >> creates lots of files, enough to push the system into the multi-pass regime. >> >> >> Pharo urgently needs to upgrade the VM to one more up to date than 2017 >> 08 27 (in fact more up-to-date than opensmalltalk/vm commit >> 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 >> -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image >> corruption in large images, and can occur (as it has here) at start-up, >> causing one's work to be irretrievably lost. >> > > Hi Eliot, > > I think that there is a lot of people who would like to get a newer > stable vm for Pharo 6.1 and 7. The problem is that it is hard to know > which VM are stable enough to be promoted as stable. > > Some weeks ago Esteban tried to promote a VM as stable and he had to > revert it the same day because a regression occurred in the VM. > > If you're able to tell us which vms are stable in those present at > http://files.pharo.org/vm/pharo-spur32/ and > http://files.pharo.org/vm/pharo-spur64/ it would be a great help. > > Even better would be for the pharo community to have a way to know which > vms are stable or not without having to ask you. there is no “stable” branch in Cog, and that’s a problem. “released” versions (the version you can find as stable) are not working for Pharo :( I tried to promote versions from end feb and that crashed. next week I will try again, maybe now they are stable enough… one thing is true: the versions that we consider stable (from oct/17) present problems that are already solved on latest. Esteban > > Have a nice day. > >> >> -- >> _,,,^..^,,,_ >> best, Eliot > -- > Cyril Ferlicot > https://ferlicot.fr >

6 10

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev April 2018