30425 ----- 11687 Merge Opal with Opal Repository https://pharo.fogbugz.com/f/cases/11687 11688 Pharo Kernel shrinking update for 30424 https://pharo.fogbugz.com/f/cases/11688 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.91... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenke... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenker...
The update build failed on Linux slave -- Pavel 2013/9/26 Marcus Denker <marcus.denker@inria.fr>:
30425 -----
11687 Merge Opal with Opal Repository https://pharo.fogbugz.com/f/cases/11687
11688 Pharo Kernel shrinking update for 30424 https://pharo.fogbugz.com/f/cases/11688
Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.91... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenke... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenker...
On Sep 26, 2013, at 8:59 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
The update build failed on Linux slave
a second run leads to the same problem. This is not goodâ¦.
-- Pavel
2013/9/26 Marcus Denker <marcus.denker@inria.fr>:
30425 -----
11687 Merge Opal with Opal Repository https://pharo.fogbugz.com/f/cases/11687
11688 Pharo Kernel shrinking update for 30424 https://pharo.fogbugz.com/f/cases/11688
Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.91... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenke... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenker...
It fails during Release test. Smalltalk stack dump: 0xbfee7364 M CompiledMethod class(Behavior)>allInstances 0x776a94b4: a(n) CompiledMethod class 0xbfee7380 M SmalltalkImage>fixObsoleteReferences 0x77916420: a(n) SmalltalkImage 0xbfee5234 M ReleaseTest>testObsoleteClasses 0x78e70cac: a(n) ReleaseTest I tried it on my local Linux machine but it worked well :-/ -- Pavel 2013/9/27 Marcus Denker <marcus.denker@inria.fr>:
On Sep 26, 2013, at 8:59 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
The update build failed on Linux slave
a second run leads to the same problem. This is not goodâ¦.
-- Pavel
2013/9/26 Marcus Denker <marcus.denker@inria.fr>:
30425 -----
11687 Merge Opal with Opal Repository https://pharo.fogbugz.com/f/cases/11687
11688 Pharo Kernel shrinking update for 30424 https://pharo.fogbugz.com/f/cases/11688
Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.91... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenke... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenker...
And it's interesting that during the first pass on a dirty image it works well even on the slave too. -- Pavel 2013/9/27 Pavel Krivanek <pavel.krivanek@gmail.com>:
It fails during Release test.
Smalltalk stack dump: 0xbfee7364 M CompiledMethod class(Behavior)>allInstances 0x776a94b4: a(n) CompiledMethod class 0xbfee7380 M SmalltalkImage>fixObsoleteReferences 0x77916420: a(n) SmalltalkImage 0xbfee5234 M ReleaseTest>testObsoleteClasses 0x78e70cac: a(n) ReleaseTest
I tried it on my local Linux machine but it worked well :-/
-- Pavel
2013/9/27 Marcus Denker <marcus.denker@inria.fr>:
On Sep 26, 2013, at 8:59 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
The update build failed on Linux slave
a second run leads to the same problem. This is not goodâ¦.
-- Pavel
2013/9/26 Marcus Denker <marcus.denker@inria.fr>:
30425 -----
11687 Merge Opal with Opal Repository https://pharo.fogbugz.com/f/cases/11687
11688 Pharo Kernel shrinking update for 30424 https://pharo.fogbugz.com/f/cases/11688
Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.91... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenke... http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenker...
On Sep 27, 2013, at 9:25 AM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
And it's interesting that during the first pass on a dirty image it works well even on the slave too.
I will revert the compiler merge for now (it did even run the regression tests⦠but showing some strange - I think - trait-recompiling related bug..) So what we will do -> revert this update (it is already auto-reverted due to the crash) -> save Opal as it is in the image before this to to the Opal repo -> get the Opal regression green (traits bug) -> get image green (we do have some failing tests) -> *then* on the Opal repo, merge step-by-the intermediate 5 small commits (Abstract compiler class, some trivial cleanups, clean block analysis that is not called) I do not see how these changes could lead to the problem, but it could be that there is some bug in the compiler that shows itself when recompiling certain methods. One interesting observation: we did not check the Opal-Regression tester for 4 weeks, and we are in the mess. This just shows how important continous integration + automatic regression testing *after every commit* is for compiler development⦠(or being more intelligent would maybe another solution ;-) Marcus
On Sep 27, 2013, at 10:08 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Sep 27, 2013, at 9:25 AM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
And it's interesting that during the first pass on a dirty image it works well even on the slave too.
I will revert the compiler merge for now
(it did even run the regression tests⦠but showing some strange - I think - trait-recompiling related bug..)
So what we will do
-> revert this update (it is already auto-reverted due to the crash) -> save Opal as it is in the image before this to to the Opal repo -> get the Opal regression green (traits bug) -> get image green (we do have some failing tests) -> *then* on the Opal repo, merge step-by-the intermediate 5 small commits (Abstract compiler class, some trivial cleanups, clean block analysis that is not called) I do not see how these changes could lead to the problem, but it could be that there is some bug in the compiler that shows itself when recompiling certain methods.
One interesting observation: we did not check the Opal-Regression tester for 4 weeks, and we are in the mess. This just shows how important continous integration + automatic regression testing *after every commit* is for compiler development⦠(or being more intelligent would maybe another solution ;-)
Result: it still fails, even after reverting. Are we sure that the VM did not change in the middle? It looks *really* strange! https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=lin... Marcus
On Sep 27, 2013, at 10:29 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Sep 27, 2013, at 10:08 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Sep 27, 2013, at 9:25 AM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
And it's interesting that during the first pass on a dirty image it works well even on the slave too.
I will revert the compiler merge for now
(it did even run the regression tests⦠but showing some strange - I think - trait-recompiling related bug..)
So what we will do
-> revert this update (it is already auto-reverted due to the crash) -> save Opal as it is in the image before this to to the Opal repo -> get the Opal regression green (traits bug) -> get image green (we do have some failing tests) -> *then* on the Opal repo, merge step-by-the intermediate 5 small commits (Abstract compiler class, some trivial cleanups, clean block analysis that is not called) I do not see how these changes could lead to the problem, but it could be that there is some bug in the compiler that shows itself when recompiling certain methods.
One interesting observation: we did not check the Opal-Regression tester for 4 weeks, and we are in the mess. This just shows how important continous integration + automatic regression testing *after every commit* is for compiler development⦠(or being more intelligent would maybe another solution ;-)
Result: it still fails, even after reverting.
Are we sure that the VM did not change in the middle? It looks *really* strange!
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=lin...
It seems someone changed the config to load the latest VM which has problems right now. I will revert that. Marcus
On Sep 27, 2013, at 10:32 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Sep 27, 2013, at 10:29 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
Result: it still fails, even after reverting.
Are we sure that the VM did not change in the middle? It looks *really* strange!
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=lin...
It seems someone changed the config to load the latest VM which has problems right now.
I will revert that.
Ok, now we can build the image again. Marcus
It was me. I tried to change the config to use the latest VM to see if it is a vm related problem. Sorry. -- Pavel 2013/9/27 Marcus Denker <marcus.denker@inria.fr>:
On Sep 27, 2013, at 10:32 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Sep 27, 2013, at 10:29 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
Result: it still fails, even after reverting.
Are we sure that the VM did not change in the middle? It looks *really* strange!
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=lin...
It seems someone changed the config to load the latest VM which has problems right now.
I will revert that.
Ok, now we can build the image again.
Marcus
participants (2)
-
Marcus Denker -
Pavel Krivanek