12 Jun
2013
12 Jun
'13
5:01 p.m.
Currently, we have a bug in the latest version of Pharo VM that does not
allow a build to complete (Esteban is working to correct it) As the builds
in Moose jenkins depend on the latest version of Pharo VM, we were unable
to perform any build since 10 days (that also includes INRIA downtime). But
the question is:
Should Moose and other builds in the moose jenkins depend on the latest VM?
Or we should depend on the stable version of the VM?
Now, stable version is good but we dont have many bug fixes that are
integrated in the latest version. For example, most of the builds in the
jenkins are now unstable and I suspect that's being caused by the fact that
we are now depending on the stable Pharo VM. I cannot verify it since the
latest VM is buggy.
Can you please see your respective builds and see why is jenkins becoming
unstable?
usman
12 Jun
12 Jun
10:22 p.m.
I think that one more option would be to make a build matrix for 2 VMs
--
View this message in context:
http://moose-dev.97923.n3.nabble.com/VM-Latest-or-Stable-tp4027859p4027864.…
Sent from the moose-dev mailing list archive at Nabble.com.
20 Jun
20 Jun
9:41 p.m.
Hi,
Moose policy is to work with the latest of Pharo as much as possible. This
implies VM and image.
We still have to get a bit more aligned with the Pharo effort on the image
side, but for the VM, we want to stress the latest version of it.
Of course, in exceptional cases, we should make exceptions. In the current
case, using stable until the bug is solved is a good solution. But this
should be an exception. In the past half a year since we moved closer to
Pharo, this is probably the first blocker that took longer than 1 day to
get fixed. Thus, the default policy of working with the head works well,
and it saves effort in the long run.
Cheers,
Doru
On Wed, Jun 12, 2013 at 5:01 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote;wrote:
Currently, we have a bug in the latest version of
Pharo VM that does not
allow a build to complete (Esteban is working to correct it) As the builds
in Moose jenkins depend on the latest version of Pharo VM, we were unable
to perform any build since 10 days (that also includes INRIA downtime). But
the question is:
Should Moose and other builds in the moose jenkins depend on the latest
VM? Or we should depend on the stable version of the VM?
Now, stable version is good but we dont have many bug fixes that are
integrated in the latest version. For example, most of the builds in the
jenkins are now unstable and I suspect that's being caused by the fact that
we are now depending on the stable Pharo VM. I cannot verify it since the
latest VM is buggy.
Can you please see your respective builds and see why is jenkins becoming
unstable?
usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
4252
days inactive
4260
days old
2 comments
3 participants
participants (3)
-
Tudor Girba -
Usman Bhatti -
Yuriy Tymchuk