I am preparing release 4.1.
I have a small failure due to XMLParserTest>>testDecodingCharacters
--- Jannik Laval
Please be sure to integrate the latest version of Mondrian. I just fixed another bug: http://code.google.com/p/moose-technology/issues/detail?id=456
Name: Mondrian-tg.573 Author: tg Time: 14 September 2010, 9:09:33 am UUID: 2081a17b-2c4a-47a7-9030-def3b98f0d6c Ancestors: Mondrian-AlexandreBergel.572
What kind of failure?
Doru
On 14 Sep 2010, at 10:15, Laval Jannik wrote:
I am preparing release 4.1.
I have a small failure due to XMLParserTest>>testDecodingCharacters
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What we can governs what we wish."
Thank you Doru, I integrate it. Now, I will test it.
For the bug, in this method: ===== testDecodingCharacters | xmlDocument element |
xmlDocument := XMLDOMParser parseDocumentFrom: self exampleEncodedXML readStream. element := xmlDocument firstTagNamed: #'test-data'.
self assert: element contentString first charCode = 8230. self assert: element contentString first leadingChar = 255. self assert: element contentString first codePoint = 1069555750 ====
The command "element contentString first leadingChar " return 0. It should return 255.
Now, I have other problems with OSProcess and UnixCommand... but, it is not part to Moose.
Cheers, Jannik
On Sep 14, 2010, at 09:20 , Tudor Girba wrote:
Please be sure to integrate the latest version of Mondrian. I just fixed another bug: http://code.google.com/p/moose-technology/issues/detail?id=456
Name: Mondrian-tg.573 Author: tg Time: 14 September 2010, 9:09:33 am UUID: 2081a17b-2c4a-47a7-9030-def3b98f0d6c Ancestors: Mondrian-AlexandreBergel.572
What kind of failure?
Doru
On 14 Sep 2010, at 10:15, Laval Jannik wrote:
I am preparing release 4.1.
I have a small failure due to XMLParserTest>>testDecodingCharacters
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"What we can governs what we wish."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--- Jannik Laval
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41. ====
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--- Jannik Laval
I am trying...
Alexandre
On 14 Sep 2010, at 13:16, Laval Jannik wrote:
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41.
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks Jannik
So the idea is that people load it, test it, and if everything is ok tomorrow we declare the official release.
On 14 sept. 2010, at 13:16, Laval Jannik wrote:
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41.
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
I loaded it in a fresh Pharo 1.1. The first thing I tried is to run all the unit tests that are installed by loading Moose. The tests of OSProcess crash the virtual machine I use (4.2.1, same result with 5.2beta3). Some failures and errors are contained in Filesystems, which is loaded by Moose.
Beside this, all the tests of the tools directly used by Moose are green. Well done guys!
Here is the summary 4234 run, 4203 passes, 22 expected failures, 7 failures, 2 errors, 0 unexpected passes A screenshot follows this email. You can easily see the culprit tests. We have to decide what to do about them. I feel they are not that important, especially if our tools that rely on Filesystem and WeakKeyHashTable are well tested. We cannot test everything, like whether the sun will rise tomorrow morning.
I run twice Moose tests. One test failed once, ModelTest>>testAddingAndRemoving I tried to executing it afterwards, it passes. This test relies on the garbage collector. There is nothing wrong in principle, however, removing a reference to an object and then triggering the garbage collector does not guaranty the object will be garbage collected. It will probably be in the future, but maybe not right away. I guess this is the reason why it went yellow.
Someone left a "self halt" in MOCanvas :-) Jannik, I created ConfigurationOfMondrian-AlexandreBergel.37, which contains an updated version of 2.0-beta.8.
I am happy with this
Cheers, Alexandre
On 14 Sep 2010, at 13:16, Laval Jannik wrote:
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41.
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I Alex, as far as i remember some problems about OSProcess have been solved by more recent VMs (there is a 4.2.5). I'm actually using that VM i did not try yet to run all tests but the OSProcess could be solved just updating the vm.
Cheers,
Fabrizio
On 14 Sep 2010, at 15:16, Alexandre Bergel wrote:
I loaded it in a fresh Pharo 1.1. The first thing I tried is to run all the unit tests that are installed by loading Moose. The tests of OSProcess crash the virtual machine I use (4.2.1, same result with 5.2beta3). Some failures and errors are contained in Filesystems, which is loaded by Moose.
Beside this, all the tests of the tools directly used by Moose are green. Well done guys!
Here is the summary 4234 run, 4203 passes, 22 expected failures, 7 failures, 2 errors, 0 unexpected passes A screenshot follows this email. You can easily see the culprit tests. We have to decide what to do about them. I feel they are not that important, especially if our tools that rely on Filesystem and WeakKeyHashTable are well tested. We cannot test everything, like whether the sun will rise tomorrow morning.
I run twice Moose tests. One test failed once, ModelTest>>testAddingAndRemoving I tried to executing it afterwards, it passes. This test relies on the garbage collector. There is nothing wrong in principle, however, removing a reference to an object and then triggering the garbage collector does not guaranty the object will be garbage collected. It will probably be in the future, but maybe not right away. I guess this is the reason why it went yellow.
Someone left a "self halt" in MOCanvas :-) Jannik, I created ConfigurationOfMondrian-AlexandreBergel.37, which contains an updated version of 2.0-beta.8.
I am happy with this
Cheers, Alexandre
<Screen shot 2010-09-14 at 14.08.50.png>
On 14 Sep 2010, at 13:16, Laval Jannik wrote:
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41.
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I run the test of OSProcess on a 64/32 5.7beta 3 (21), and indeed, the vm does not crash. But I get 190 run, 30 passes, 0 expected failures, 135 failures, 25 errors, 0 unexpected passes.
Alexandre
On 14 Sep 2010, at 14:26, Fabrizio Perin wrote:
I Alex, as far as i remember some problems about OSProcess have been solved by more recent VMs (there is a 4.2.5). I'm actually using that VM i did not try yet to run all tests but the OSProcess could be solved just updating the vm.
Cheers,
Fabrizio
On 14 Sep 2010, at 15:16, Alexandre Bergel wrote:
I loaded it in a fresh Pharo 1.1. The first thing I tried is to run all the unit tests that are installed by loading Moose. The tests of OSProcess crash the virtual machine I use (4.2.1, same result with 5.2beta3). Some failures and errors are contained in Filesystems, which is loaded by Moose.
Beside this, all the tests of the tools directly used by Moose are green. Well done guys!
Here is the summary 4234 run, 4203 passes, 22 expected failures, 7 failures, 2 errors, 0 unexpected passes A screenshot follows this email. You can easily see the culprit tests. We have to decide what to do about them. I feel they are not that important, especially if our tools that rely on Filesystem and WeakKeyHashTable are well tested. We cannot test everything, like whether the sun will rise tomorrow morning.
I run twice Moose tests. One test failed once, ModelTest>>testAddingAndRemoving I tried to executing it afterwards, it passes. This test relies on the garbage collector. There is nothing wrong in principle, however, removing a reference to an object and then triggering the garbage collector does not guaranty the object will be garbage collected. It will probably be in the future, but maybe not right away. I guess this is the reason why it went yellow.
Someone left a "self halt" in MOCanvas :-) Jannik, I created ConfigurationOfMondrian-AlexandreBergel.37, which contains an updated version of 2.0-beta.8.
I am happy with this
Cheers, Alexandre
<Screen shot 2010-09-14 at 14.08.50.png>
On 14 Sep 2010, at 13:16, Laval Jannik wrote:
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41.
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks everyone for all the work on preparing 4.1. I am now building the release.
Cheers, Doru
On 14 Sep 2010, at 15:41, Alexandre Bergel wrote:
I run the test of OSProcess on a 64/32 5.7beta 3 (21), and indeed, the vm does not crash. But I get 190 run, 30 passes, 0 expected failures, 135 failures, 25 errors, 0 unexpected passes.
Alexandre
On 14 Sep 2010, at 14:26, Fabrizio Perin wrote:
I Alex, as far as i remember some problems about OSProcess have been solved by more recent VMs (there is a 4.2.5). I'm actually using that VM i did not try yet to run all tests but the OSProcess could be solved just updating the vm.
Cheers,
Fabrizio
On 14 Sep 2010, at 15:16, Alexandre Bergel wrote:
I loaded it in a fresh Pharo 1.1. The first thing I tried is to run all the unit tests that are installed by loading Moose. The tests of OSProcess crash the virtual machine I use (4.2.1, same result with 5.2beta3). Some failures and errors are contained in Filesystems, which is loaded by Moose.
Beside this, all the tests of the tools directly used by Moose are green. Well done guys!
Here is the summary 4234 run, 4203 passes, 22 expected failures, 7 failures, 2 errors, 0 unexpected passes A screenshot follows this email. You can easily see the culprit tests. We have to decide what to do about them. I feel they are not that important, especially if our tools that rely on Filesystem and WeakKeyHashTable are well tested. We cannot test everything, like whether the sun will rise tomorrow morning.
I run twice Moose tests. One test failed once, ModelTest>>testAddingAndRemoving I tried to executing it afterwards, it passes. This test relies on the garbage collector. There is nothing wrong in principle, however, removing a reference to an object and then triggering the garbage collector does not guaranty the object will be garbage collected. It will probably be in the future, but maybe not right away. I guess this is the reason why it went yellow.
Someone left a "self halt" in MOCanvas :-) Jannik, I created ConfigurationOfMondrian-AlexandreBergel.37, which contains an updated version of 2.0-beta.8.
I am happy with this
Cheers, Alexandre
<Screen shot 2010-09-14 at 14.08.50.png>
On 14 Sep 2010, at 13:16, Laval Jannik wrote:
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41.
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every successful trip needs a suitable vehicle."
Thanks Alex,
I have the same problems.
Cheers, Janik
On Sep 14, 2010, at 14:16 , Alexandre Bergel wrote:
I loaded it in a fresh Pharo 1.1. The first thing I tried is to run all the unit tests that are installed by loading Moose. The tests of OSProcess crash the virtual machine I use (4.2.1, same result with 5.2beta3). Some failures and errors are contained in Filesystems, which is loaded by Moose.
Beside this, all the tests of the tools directly used by Moose are green. Well done guys!
Here is the summary 4234 run, 4203 passes, 22 expected failures, 7 failures, 2 errors, 0 unexpected passes A screenshot follows this email. You can easily see the culprit tests. We have to decide what to do about them. I feel they are not that important, especially if our tools that rely on Filesystem and WeakKeyHashTable are well tested. We cannot test everything, like whether the sun will rise tomorrow morning.
I run twice Moose tests. One test failed once, ModelTest>>testAddingAndRemoving I tried to executing it afterwards, it passes. This test relies on the garbage collector. There is nothing wrong in principle, however, removing a reference to an object and then triggering the garbage collector does not guaranty the object will be garbage collected. It will probably be in the future, but maybe not right away. I guess this is the reason why it went yellow.
Someone left a "self halt" in MOCanvas :-) Jannik, I created ConfigurationOfMondrian-AlexandreBergel.37, which contains an updated version of 2.0-beta.8.
I am happy with this
Cheers, Alexandre
<Screen shot 2010-09-14 at 14.08.50.png>
On 14 Sep 2010, at 13:16, Laval Jannik wrote:
Ok, you can load Moose4.1 with:
==== Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease41.
On Sep 14, 2010, at 09:32 , Alexandre Bergel wrote:
I have a small failure due to XMLParserTest>>testDecodingCharacters
yeah, there has been this failure for a while already. No user of XMLParser has been able to fix it. I will send another call.
Alexandre
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Jannik Laval
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--- Jannik Laval
-
Alexandre Bergel -
Fabrizio Perin -
Laval Jannik -
Simon Denier -
Tudor Girba