smalltalkCI Trunk broken: vmParameterAt:put: failed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

smalltalkCI Trunk broken: vmParameterAt:put: failed

Jakob Reschke-2
Hello,

Christoph's idea of having alerts whenever the Trunk builds in
smalltalkCI get broken sounds like a good one. @Fabio is it possible
to set up a dummy repository that does not really load anything, but
runs the Squeak base test suite? Or load an empty dummy package and
run the test suite of a different package?

This time something goes wrong while setting a VM parameter.
Unfortunately it does not tell you where it really happens:

Preparing Squeak64-trunk image for CI...
................................................Error: vmParameterAt:put: failed

https://travis-ci.org/hpi-swa/Squot/jobs/659875037

(You only see the error in the raw log towards the bottom:
https://api.travis-ci.org/v3/job/659875037/log.txt, but there is no
additional info to what I pasted above)

Kind regards,
Jakob

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

timrowledge


> On 2020-03-10, at 12:08 PM, Jakob Reschke <[hidden email]> wrote:
>
> Hello,
>
> Christoph's idea of having alerts whenever the Trunk builds in
> smalltalkCI get broken sounds like a good one. @Fabio is it possible
> to set up a dummy repository that does not really load anything, but
> runs the Squeak base test suite? Or load an empty dummy package and
> run the test suite of a different package?
>
> This time something goes wrong while setting a VM parameter.
> Unfortunately it does not tell you where it really happens:
>
> Preparing Squeak64-trunk image for CI...
> ................................................Error: vmParameterAt:put: failed

That sounds interestingly similar to the problem I reported with the linuxARMv6 vm in the 5.3 release package...


tim

Give a man a compliment, he’ll feel good for a day.
Teach a man to fish for compliments and he’ll never feel good enough for the rest of his life.


Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Eliot Miranda-2


On Tue, Mar 10, 2020 at 12:13 PM tim Rowledge <[hidden email]> wrote:


> On 2020-03-10, at 12:08 PM, Jakob Reschke <[hidden email]> wrote:
>
> Hello,
>
> Christoph's idea of having alerts whenever the Trunk builds in
> smalltalkCI get broken sounds like a good one. @Fabio is it possible
> to set up a dummy repository that does not really load anything, but
> runs the Squeak base test suite? Or load an empty dummy package and
> run the test suite of a different package?
>
> This time something goes wrong while setting a VM parameter.
> Unfortunately it does not tell you where it really happens:
>
> Preparing Squeak64-trunk image for CI...
> ................................................Error: vmParameterAt:put: failed

That sounds interestingly similar to the problem I reported with the linuxARMv6 vm in the 5.3 release package...

Any stack traces?  Which parameter, which value was being assigned, etc?

"Something went wrong" is rather vague...

_,,,^..^,,,_
best, Eliot


Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Jakob Reschke-2
Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
<[hidden email]>:

>
> On Tue, Mar 10, 2020 at 12:13 PM tim Rowledge <[hidden email]> wrote:
>>
>> > On 2020-03-10, at 12:08 PM, Jakob Reschke <[hidden email]> wrote:
>> >
>> > Hello,
>> >
>> > Christoph's idea of having alerts whenever the Trunk builds in
>> > smalltalkCI get broken sounds like a good one. @Fabio is it possible
>> > to set up a dummy repository that does not really load anything, but
>> > runs the Squeak base test suite? Or load an empty dummy package and
>> > run the test suite of a different package?
>> >
>> > This time something goes wrong while setting a VM parameter.
>> > Unfortunately it does not tell you where it really happens:
>> >
>> > Preparing Squeak64-trunk image for CI...
>> > ................................................Error: vmParameterAt:put: failed
>>
>> That sounds interestingly similar to the problem I reported with the linuxARMv6 vm in the 5.3 release package...
>
>
> Any stack traces?  Which parameter, which value was being assigned, etc?
>
> "Something went wrong" is rather vague...

I know, unfortunately Travis does not provide any more specific output. :-(
Maybe I can try to run smalltalkCI on my machine later and see whether
that gives anything.

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

timrowledge
In reply to this post by Eliot Miranda-2


> On 2020-03-10, at 12:42 PM, Eliot Miranda <[hidden email]> wrote:
>
> Any stack traces?  Which parameter, which value was being assigned, etc?
>
> "Something went wrong" is rather vague...

On the ARMv6 vm it was logged as in SmalltalkImage>setGCParameters where we read param 44 and set param 6. Haven't had time to try to remember how I set up build/debug to go any further into it yet. And I can't for the life of me see why /lib/arm-linux-gnueabihf/libc.so.6(vsprintf+0x80)[0x76c89228] got involved... unless sometihng is/was broken in a trampoline thing? Returning to completely nonsensical places usually doesn't work out so well.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Half the people you know are below average.



Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Eliot Miranda-2
Hi Tim,

On Tue, Mar 10, 2020 at 1:46 PM tim Rowledge <[hidden email]> wrote:


> On 2020-03-10, at 12:42 PM, Eliot Miranda <[hidden email]> wrote:
>
> Any stack traces?  Which parameter, which value was being assigned, etc?
>
> "Something went wrong" is rather vague...

On the ARMv6 vm it was logged as in SmalltalkImage>setGCParameters where we read param 44 and set param 6. Haven't had time to try to remember how I set up build/debug to go any further into it yet. And I can't for the life of me see why /lib/arm-linux-gnueabihf/libc.so.6(vsprintf+0x80)[0x76c89228] got involved... unless sometihng is/was broken in a trampoline thing? Returning to completely nonsensical places usually doesn't work out so well.

If you run it in gdb what's the back trace from the crash and the top stack frame? (printExternalHeadFrame)

Does it crash on Raspberry Pi 4?  (I'd have to disinter my Pi 2 & 3...)

_,,,^..^,,,_
best, Eliot


Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

fniephaus
In reply to this post by Jakob Reschke-2
I feel like this might have something to do with us enabling Sista while using relatively old VMs for trunk images on CI.

Can anyone verify that the VMs running on Travis come with the Sista bytecode set? 

Fabio

On Tue, 10 Mar 2020 at 8:48 pm, Jakob Reschke <[hidden email]> wrote:
Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
<[hidden email]>:
>
> On Tue, Mar 10, 2020 at 12:13 PM tim Rowledge <[hidden email]> wrote:
>>
>> > On 2020-03-10, at 12:08 PM, Jakob Reschke <[hidden email]> wrote:
>> >
>> > Hello,
>> >
>> > Christoph's idea of having alerts whenever the Trunk builds in
>> > smalltalkCI get broken sounds like a good one. @Fabio is it possible
>> > to set up a dummy repository that does not really load anything, but
>> > runs the Squeak base test suite? Or load an empty dummy package and
>> > run the test suite of a different package?
>> >
>> > This time something goes wrong while setting a VM parameter.
>> > Unfortunately it does not tell you where it really happens:
>> >
>> > Preparing Squeak64-trunk image for CI...
>> > ................................................Error: vmParameterAt:put: failed
>>
>> That sounds interestingly similar to the problem I reported with the linuxARMv6 vm in the 5.3 release package...
>
>
> Any stack traces?  Which parameter, which value was being assigned, etc?
>
> "Something went wrong" is rather vague...

I know, unfortunately Travis does not provide any more specific output. :-(
Maybe I can try to run smalltalkCI on my machine later and see whether
that gives anything.



Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

fniephaus
In reply to this post by Jakob Reschke-2

On Tue, 10 Mar 2020 at 8:08 pm, Jakob Reschke <[hidden email]> wrote:
Hello,

Christoph's idea of having alerts whenever the Trunk builds in
smalltalkCI get broken sounds like a good one. @Fabio is it possible
to set up a dummy repository that does not really load anything, but
runs the Squeak base test suite? Or load an empty dummy package and
run the test suite of a different package?

We're already doing just that, see

The problem is that no one checks the trunk build status on Slack, and the admins of this mailing list haven't allowed Travis to send notification emails (they come from [hidden email] I think).

Fabio



This time something goes wrong while setting a VM parameter.
Unfortunately it does not tell you where it really happens:

Preparing Squeak64-trunk image for CI...
................................................Error: vmParameterAt:put: failed

https://travis-ci.org/hpi-swa/Squot/jobs/659875037

(You only see the error in the raw log towards the bottom:
https://api.travis-ci.org/v3/job/659875037/log.txt, but there is no
additional info to what I pasted above)

Kind regards,
Jakob



Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

marcel.taeumel
In reply to this post by fniephaus
Can anyone verify that the VMs running on Travis come with the Sista bytecode set? 

Both Squeak 5.2 and Squeak 5.3 release VMs support the SistaV1 bytecode set.

Best,
Marcel

Am 10.03.2020 23:13:06 schrieb Fabio Niephaus <[hidden email]>:

I feel like this might have something to do with us enabling Sista while using relatively old VMs for trunk images on CI.

Can anyone verify that the VMs running on Travis come with the Sista bytecode set? 

Fabio

On Tue, 10 Mar 2020 at 8:48 pm, Jakob Reschke <[hidden email]> wrote:
Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
<[hidden email]>:
>
> On Tue, Mar 10, 2020 at 12:13 PM tim Rowledge <[hidden email]> wrote:
>>
>> > On 2020-03-10, at 12:08 PM, Jakob Reschke <[hidden email]> wrote:
>> >
>> > Hello,
>> >
>> > Christoph's idea of having alerts whenever the Trunk builds in
>> > smalltalkCI get broken sounds like a good one. @Fabio is it possible
>> > to set up a dummy repository that does not really load anything, but
>> > runs the Squeak base test suite? Or load an empty dummy package and
>> > run the test suite of a different package?
>> >
>> > This time something goes wrong while setting a VM parameter.
>> > Unfortunately it does not tell you where it really happens:
>> >
>> > Preparing Squeak64-trunk image for CI...
>> > ................................................Error: vmParameterAt:put: failed
>>
>> That sounds interestingly similar to the problem I reported with the linuxARMv6 vm in the 5.3 release package...
>
>
> Any stack traces?  Which parameter, which value was being assigned, etc?
>
> "Something went wrong" is rather vague...

I know, unfortunately Travis does not provide any more specific output. :-(
Maybe I can try to run smalltalkCI on my machine later and see whether
that gives anything.



Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Eliot Miranda-2
In reply to this post by fniephaus


On Tue, Mar 10, 2020 at 3:13 PM Fabio Niephaus <[hidden email]> wrote:
I feel like this might have something to do with us enabling Sista while using relatively old VMs for trunk images on CI.

Can anyone verify that the VMs running on Travis come with the Sista bytecode set? 

Which one does using vmParameterAt: 65:

65 In newer Cog VMs a set of flags describing VM features,
if non-zero bit 0 implies multiple bytecode set support;
if non-zero bit 1 implies read-only object support
(read-only; Cog VMs only; nil in older Cog VMs, a boolean answering multiple bytecode support in not so old Cog VMs)
 

Fabio

On Tue, 10 Mar 2020 at 8:48 pm, Jakob Reschke <[hidden email]> wrote:
Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
<[hidden email]>:
>
> On Tue, Mar 10, 2020 at 12:13 PM tim Rowledge <[hidden email]> wrote:
>>
>> > On 2020-03-10, at 12:08 PM, Jakob Reschke <[hidden email]> wrote:
>> >
>> > Hello,
>> >
>> > Christoph's idea of having alerts whenever the Trunk builds in
>> > smalltalkCI get broken sounds like a good one. @Fabio is it possible
>> > to set up a dummy repository that does not really load anything, but
>> > runs the Squeak base test suite? Or load an empty dummy package and
>> > run the test suite of a different package?
>> >
>> > This time something goes wrong while setting a VM parameter.
>> > Unfortunately it does not tell you where it really happens:
>> >
>> > Preparing Squeak64-trunk image for CI...
>> > ................................................Error: vmParameterAt:put: failed
>>
>> That sounds interestingly similar to the problem I reported with the linuxARMv6 vm in the 5.3 release package...
>
>
> Any stack traces?  Which parameter, which value was being assigned, etc?
>
> "Something went wrong" is rather vague...

I know, unfortunately Travis does not provide any more specific output. :-(
Maybe I can try to run smalltalkCI on my machine later and see whether
that gives anything.




--
_,,,^..^,,,_
best, Eliot


Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Jakob Reschke-2
In reply to this post by Jakob Reschke-2
Am Di., 10. März 2020 um 20:47 Uhr schrieb Jakob Reschke
<[hidden email]>:

>
> Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
> <[hidden email]>:
> >
> > Any stack traces?  Which parameter, which value was being assigned, etc?
> >
> > "Something went wrong" is rather vague...
>
> I know, unfortunately Travis does not provide any more specific output. :-(
> Maybe I can try to run smalltalkCI on my machine later and see whether
> that gives anything.

I finally got around to try a local build. But still no debug log or
crash dump to be found.
The Trunk builds are still failing, while the 5.2 builds are fine.

@Fabio: should I look anywhere else than in the build directory? This
is the listing:

jakob@JAKOBS-PC:~/smalltalkCI/_builds/2020_03_23_20_39_33$ ls -la
insgesamt 135648
drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:44 .
drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:39 ..
-rw-rw-rw- 1 jakob jakob      496 Mär 23 20:39 coveralls_build_data.json
-rw-rw-rw- 1 jakob jakob      390 Mär 23 20:44 load.st
drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:43 package-cache
-rw-rw-rw- 1 jakob jakob     1961 Mär 23 20:39 prepare.st
-rw-r--r-- 1 jakob jakob      120 Dez  6  2018
._Squeak5.3alpha-18294-64bit.changes
-rw-r--r-- 1 jakob jakob      268 Dez  6  2018
._Squeak5.3alpha-18294-64bit.image
-rw-rw-rw- 1 jakob jakob 26874889 Mär 23 20:39 Squeak64-trunk.tar.gz
-rw-r--r-- 1 jakob jakob      212 Okt  8  2018 ._SqueakV50.sources
-rw-r--r-- 1 jakob jakob 35184983 Okt  8  2018 SqueakV50.sources
-rw-r--r-- 1 jakob jakob 20592231 Mär 23 20:44 TravisCI.changes
-rw-r--r-- 1 jakob jakob 54393712 Mär 23 20:44 TravisCI.image
-rwxrwxrwx 1 jakob jakob       79 Mär 23 20:39 vm

If I should send any files, please tell me.

Note that this is on Windows Subsystem for Linux, but it didn't make
any difference in the past.
The smalltalkCI output is the same as on Travis: (see below).

During the headful run, I could watch it recompiling all methods
(presumably after switching Sista on?), and quickly after that Squeak
shut down. But I cannot tell whether it did so cleanly or not.

Kind regards,
Jakob


jakob@JAKOBS-PC:~/smalltalkCI$ bin/smalltalkci --headful
/mnt/c/Squeak/MA/Squot-Squit/.smalltalk.ston
 1) Squeak64-trunk      15) Pharo64-8.0         29) GemStone64-3.4.3
 2) Squeak64-5.3        16) Pharo64-7.0         30) GemStone64-3.3.9
 3) Squeak64-5.2        17) Pharo64-6.1         31) GemStone64-3.3.2
 4) Squeak64-5.1        18) Pharo64-6.0         32) GemStone64-3.3.0
 5) Squeak32-trunk      19) Pharo32-stable      33) GemStone64-3.2.12
 6) Squeak32-5.3        20) Pharo32-alpha       34) GemStone64-3.1.0.6
 7) Squeak32-5.2        21) Pharo32-9.0         35) Moose64-trunk
 8) Squeak32-5.1        22) Pharo32-8.0         36) Moose64-8.0
 9) Squeak32-5.0        23) Pharo32-7.0         37) Moose64-7.0
10) Squeak32-4.6        24) Pharo32-6.0         38) Moose32-trunk
11) Squeak32-4.5        25) Pharo32-5.0         39) Moose32-8.0
12) Pharo64-stable      26) Pharo32-4.0         40) Moose32-7.0
13) Pharo64-alpha       27) Pharo32-3.0         41) Moose32-6.1
14) Pharo64-9.0         28) GemStone64-3.5.0    42) Moose32-6.0
Choose Smalltalk image: 1
Preparing folders...
Starting Squeak build...
Downloading Squeak64-trunk image...
 > Time to run: 6.288s
Cog VM Information
5.0-201810190412  Sat Oct 20 08:17:23 UTC 2018 gcc 4.8 [Production
Spur 64-bit ITHB VM]
CoInterpreter VMMaker.oscog-eem.2461 uuid:
b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 20 2018
StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid:
0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 20 2018
VM: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Date: Thu Oct 18 21:12:21 2018 CommitHash: 15341b57
Plugins: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Linux travis-job-7e855ac8-57b9-4f6f-bf30-fd6e0ad67398
4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
plugin path: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412
[default: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412/]
 > Time to run: 0.061s
Preparing Squeak64-trunk image for CI...
........................................................Error:
vmParameterAt:put: failed > Time to run: 275.810s
Build was unable to report intermediate build status.
cat: /home/jakob/smalltalkCI/_builds/2020_03_23_20_39_33/build_status.txt:
Datei oder Verzeichnis nicht gefunden

Error with status code 1:
237 check_and_consume_build_status_file /home/jakob/smalltalkCI/helpers.sh

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Nicolas Cellier
Hi Jakob,
I think that I put in 6.0 trunk a postscript instruction that activates the delivery of mouse wheel events.
This requires an updated VM on windows (I honoured this request by end of 2019).
So the question is why is the VM so old?

Le lun. 23 mars 2020 à 20:59, Jakob Reschke <[hidden email]> a écrit :
Am Di., 10. März 2020 um 20:47 Uhr schrieb Jakob Reschke
<[hidden email]>:
>
> Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
> <[hidden email]>:
> >
> > Any stack traces?  Which parameter, which value was being assigned, etc?
> >
> > "Something went wrong" is rather vague...
>
> I know, unfortunately Travis does not provide any more specific output. :-(
> Maybe I can try to run smalltalkCI on my machine later and see whether
> that gives anything.

I finally got around to try a local build. But still no debug log or
crash dump to be found.
The Trunk builds are still failing, while the 5.2 builds are fine.

@Fabio: should I look anywhere else than in the build directory? This
is the listing:

jakob@JAKOBS-PC:~/smalltalkCI/_builds/2020_03_23_20_39_33$ ls -la
insgesamt 135648
drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:44 .
drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:39 ..
-rw-rw-rw- 1 jakob jakob      496 Mär 23 20:39 coveralls_build_data.json
-rw-rw-rw- 1 jakob jakob      390 Mär 23 20:44 load.st
drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:43 package-cache
-rw-rw-rw- 1 jakob jakob     1961 Mär 23 20:39 prepare.st
-rw-r--r-- 1 jakob jakob      120 Dez  6  2018
._Squeak5.3alpha-18294-64bit.changes
-rw-r--r-- 1 jakob jakob      268 Dez  6  2018
._Squeak5.3alpha-18294-64bit.image
-rw-rw-rw- 1 jakob jakob 26874889 Mär 23 20:39 Squeak64-trunk.tar.gz
-rw-r--r-- 1 jakob jakob      212 Okt  8  2018 ._SqueakV50.sources
-rw-r--r-- 1 jakob jakob 35184983 Okt  8  2018 SqueakV50.sources
-rw-r--r-- 1 jakob jakob 20592231 Mär 23 20:44 TravisCI.changes
-rw-r--r-- 1 jakob jakob 54393712 Mär 23 20:44 TravisCI.image
-rwxrwxrwx 1 jakob jakob       79 Mär 23 20:39 vm

If I should send any files, please tell me.

Note that this is on Windows Subsystem for Linux, but it didn't make
any difference in the past.
The smalltalkCI output is the same as on Travis: (see below).

During the headful run, I could watch it recompiling all methods
(presumably after switching Sista on?), and quickly after that Squeak
shut down. But I cannot tell whether it did so cleanly or not.

Kind regards,
Jakob


jakob@JAKOBS-PC:~/smalltalkCI$ bin/smalltalkci --headful
/mnt/c/Squeak/MA/Squot-Squit/.smalltalk.ston
 1) Squeak64-trunk      15) Pharo64-8.0         29) GemStone64-3.4.3
 2) Squeak64-5.3        16) Pharo64-7.0         30) GemStone64-3.3.9
 3) Squeak64-5.2        17) Pharo64-6.1         31) GemStone64-3.3.2
 4) Squeak64-5.1        18) Pharo64-6.0         32) GemStone64-3.3.0
 5) Squeak32-trunk      19) Pharo32-stable      33) GemStone64-3.2.12
 6) Squeak32-5.3        20) Pharo32-alpha       34) GemStone64-3.1.0.6
 7) Squeak32-5.2        21) Pharo32-9.0         35) Moose64-trunk
 8) Squeak32-5.1        22) Pharo32-8.0         36) Moose64-8.0
 9) Squeak32-5.0        23) Pharo32-7.0         37) Moose64-7.0
10) Squeak32-4.6        24) Pharo32-6.0         38) Moose32-trunk
11) Squeak32-4.5        25) Pharo32-5.0         39) Moose32-8.0
12) Pharo64-stable      26) Pharo32-4.0         40) Moose32-7.0
13) Pharo64-alpha       27) Pharo32-3.0         41) Moose32-6.1
14) Pharo64-9.0         28) GemStone64-3.5.0    42) Moose32-6.0
Choose Smalltalk image: 1
Preparing folders...
Starting Squeak build...
Downloading Squeak64-trunk image...
 > Time to run: 6.288s
Cog VM Information
5.0-201810190412  Sat Oct 20 08:17:23 UTC 2018 gcc 4.8 [Production
Spur 64-bit ITHB VM]
CoInterpreter VMMaker.oscog-eem.2461 uuid:
b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 20 2018
StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid:
0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 20 2018
VM: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Date: Thu Oct 18 21:12:21 2018 CommitHash: 15341b57
Plugins: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Linux travis-job-7e855ac8-57b9-4f6f-bf30-fd6e0ad67398
4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
plugin path: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412
[default: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412/]
 > Time to run: 0.061s
Preparing Squeak64-trunk image for CI...
........................................................Error:
vmParameterAt:put: failed > Time to run: 275.810s
Build was unable to report intermediate build status.
cat: /home/jakob/smalltalkCI/_builds/2020_03_23_20_39_33/build_status.txt:
Datei oder Verzeichnis nicht gefunden

Error with status code 1:
237 check_and_consume_build_status_file /home/jakob/smalltalkCI/helpers.sh



Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Jakob Reschke-2
The VMs are pulled by smalltalkCI, I have no control over that. Or have I?

Also note that this is a Linux Squeak VM, running under the Linux
subsystem, not a Windows Squeak VM.

Am Mo., 23. März 2020 um 21:07 Uhr schrieb Nicolas Cellier
<[hidden email]>:

>
> Hi Jakob,
> I think that I put in 6.0 trunk a postscript instruction that activates the delivery of mouse wheel events.
> This requires an updated VM on windows (I honoured this request by end of 2019).
> So the question is why is the VM so old?
>
> Le lun. 23 mars 2020 à 20:59, Jakob Reschke <[hidden email]> a écrit :
>>
>> Am Di., 10. März 2020 um 20:47 Uhr schrieb Jakob Reschke
>> <[hidden email]>:
>> >
>> > Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
>> > <[hidden email]>:
>> > >
>> > > Any stack traces?  Which parameter, which value was being assigned, etc?
>> > >
>> > > "Something went wrong" is rather vague...
>> >
>> > I know, unfortunately Travis does not provide any more specific output. :-(
>> > Maybe I can try to run smalltalkCI on my machine later and see whether
>> > that gives anything.
>>
>> I finally got around to try a local build. But still no debug log or
>> crash dump to be found.
>> The Trunk builds are still failing, while the 5.2 builds are fine.
>>
>> @Fabio: should I look anywhere else than in the build directory? This
>> is the listing:
>>
>> jakob@JAKOBS-PC:~/smalltalkCI/_builds/2020_03_23_20_39_33$ ls -la
>> insgesamt 135648
>> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:44 .
>> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:39 ..
>> -rw-rw-rw- 1 jakob jakob      496 Mär 23 20:39 coveralls_build_data.json
>> -rw-rw-rw- 1 jakob jakob      390 Mär 23 20:44 load.st
>> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:43 package-cache
>> -rw-rw-rw- 1 jakob jakob     1961 Mär 23 20:39 prepare.st
>> -rw-r--r-- 1 jakob jakob      120 Dez  6  2018
>> ._Squeak5.3alpha-18294-64bit.changes
>> -rw-r--r-- 1 jakob jakob      268 Dez  6  2018
>> ._Squeak5.3alpha-18294-64bit.image
>> -rw-rw-rw- 1 jakob jakob 26874889 Mär 23 20:39 Squeak64-trunk.tar.gz
>> -rw-r--r-- 1 jakob jakob      212 Okt  8  2018 ._SqueakV50.sources
>> -rw-r--r-- 1 jakob jakob 35184983 Okt  8  2018 SqueakV50.sources
>> -rw-r--r-- 1 jakob jakob 20592231 Mär 23 20:44 TravisCI.changes
>> -rw-r--r-- 1 jakob jakob 54393712 Mär 23 20:44 TravisCI.image
>> -rwxrwxrwx 1 jakob jakob       79 Mär 23 20:39 vm
>>
>> If I should send any files, please tell me.
>>
>> Note that this is on Windows Subsystem for Linux, but it didn't make
>> any difference in the past.
>> The smalltalkCI output is the same as on Travis: (see below).
>>
>> During the headful run, I could watch it recompiling all methods
>> (presumably after switching Sista on?), and quickly after that Squeak
>> shut down. But I cannot tell whether it did so cleanly or not.
>>
>> Kind regards,
>> Jakob
>>
>>
>> jakob@JAKOBS-PC:~/smalltalkCI$ bin/smalltalkci --headful
>> /mnt/c/Squeak/MA/Squot-Squit/.smalltalk.ston
>>  1) Squeak64-trunk      15) Pharo64-8.0         29) GemStone64-3.4.3
>>  2) Squeak64-5.3        16) Pharo64-7.0         30) GemStone64-3.3.9
>>  3) Squeak64-5.2        17) Pharo64-6.1         31) GemStone64-3.3.2
>>  4) Squeak64-5.1        18) Pharo64-6.0         32) GemStone64-3.3.0
>>  5) Squeak32-trunk      19) Pharo32-stable      33) GemStone64-3.2.12
>>  6) Squeak32-5.3        20) Pharo32-alpha       34) GemStone64-3.1.0.6
>>  7) Squeak32-5.2        21) Pharo32-9.0         35) Moose64-trunk
>>  8) Squeak32-5.1        22) Pharo32-8.0         36) Moose64-8.0
>>  9) Squeak32-5.0        23) Pharo32-7.0         37) Moose64-7.0
>> 10) Squeak32-4.6        24) Pharo32-6.0         38) Moose32-trunk
>> 11) Squeak32-4.5        25) Pharo32-5.0         39) Moose32-8.0
>> 12) Pharo64-stable      26) Pharo32-4.0         40) Moose32-7.0
>> 13) Pharo64-alpha       27) Pharo32-3.0         41) Moose32-6.1
>> 14) Pharo64-9.0         28) GemStone64-3.5.0    42) Moose32-6.0
>> Choose Smalltalk image: 1
>> Preparing folders...
>> Starting Squeak build...
>> Downloading Squeak64-trunk image...
>>  > Time to run: 6.288s
>> Cog VM Information
>> 5.0-201810190412  Sat Oct 20 08:17:23 UTC 2018 gcc 4.8 [Production
>> Spur 64-bit ITHB VM]
>> CoInterpreter VMMaker.oscog-eem.2461 uuid:
>> b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 20 2018
>> StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid:
>> 0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 20 2018
>> VM: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
>> Date: Thu Oct 18 21:12:21 2018 CommitHash: 15341b57
>> Plugins: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
>> Linux travis-job-7e855ac8-57b9-4f6f-bf30-fd6e0ad67398
>> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017
>> x86_64 x86_64 x86_64 GNU/Linux
>> plugin path: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412
>> [default: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412/]
>>  > Time to run: 0.061s
>> Preparing Squeak64-trunk image for CI...
>> ........................................................Error:
>> vmParameterAt:put: failed > Time to run: 275.810s
>> Build was unable to report intermediate build status.
>> cat: /home/jakob/smalltalkCI/_builds/2020_03_23_20_39_33/build_status.txt:
>> Datei oder Verzeichnis nicht gefunden
>>
>> Error with status code 1:
>> 237 check_and_consume_build_status_file /home/jakob/smalltalkCI/helpers.sh
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Nicolas Cellier


Le lun. 23 mars 2020 à 21:12, Jakob Reschke <[hidden email]> a écrit :
The VMs are pulled by smalltalkCI, I have no control over that. Or have I?

Maybe check the smalltalkCI scripts and send a pull request (or simply open an issue: Squeak32/64-trunk and 5.3 should use VM from 2020).

Also note that this is a Linux Squeak VM, running under the Linux
subsystem, not a Windows Squeak VM.

Ah yes, sorry,
I also compile and test spur64 on wsl from time to time, so should better reconnect my mind ;)
Let me see, introduction of wheel events support is from Nov 2018

So VM 5.0-201810190412 is still too old on linux too, not only on windows.

Am Mo., 23. März 2020 um 21:07 Uhr schrieb Nicolas Cellier
<[hidden email]>:
>
> Hi Jakob,
> I think that I put in 6.0 trunk a postscript instruction that activates the delivery of mouse wheel events.
> This requires an updated VM on windows (I honoured this request by end of 2019).
> So the question is why is the VM so old?
>
> Le lun. 23 mars 2020 à 20:59, Jakob Reschke <[hidden email]> a écrit :
>>
>> Am Di., 10. März 2020 um 20:47 Uhr schrieb Jakob Reschke
>> <[hidden email]>:
>> >
>> > Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
>> > <[hidden email]>:
>> > >
>> > > Any stack traces?  Which parameter, which value was being assigned, etc?
>> > >
>> > > "Something went wrong" is rather vague...
>> >
>> > I know, unfortunately Travis does not provide any more specific output. :-(
>> > Maybe I can try to run smalltalkCI on my machine later and see whether
>> > that gives anything.
>>
>> I finally got around to try a local build. But still no debug log or
>> crash dump to be found.
>> The Trunk builds are still failing, while the 5.2 builds are fine.
>>
>> @Fabio: should I look anywhere else than in the build directory? This
>> is the listing:
>>
>> jakob@JAKOBS-PC:~/smalltalkCI/_builds/2020_03_23_20_39_33$ ls -la
>> insgesamt 135648
>> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:44 .
>> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:39 ..
>> -rw-rw-rw- 1 jakob jakob      496 Mär 23 20:39 coveralls_build_data.json
>> -rw-rw-rw- 1 jakob jakob      390 Mär 23 20:44 load.st
>> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:43 package-cache
>> -rw-rw-rw- 1 jakob jakob     1961 Mär 23 20:39 prepare.st
>> -rw-r--r-- 1 jakob jakob      120 Dez  6  2018
>> ._Squeak5.3alpha-18294-64bit.changes
>> -rw-r--r-- 1 jakob jakob      268 Dez  6  2018
>> ._Squeak5.3alpha-18294-64bit.image
>> -rw-rw-rw- 1 jakob jakob 26874889 Mär 23 20:39 Squeak64-trunk.tar.gz
>> -rw-r--r-- 1 jakob jakob      212 Okt  8  2018 ._SqueakV50.sources
>> -rw-r--r-- 1 jakob jakob 35184983 Okt  8  2018 SqueakV50.sources
>> -rw-r--r-- 1 jakob jakob 20592231 Mär 23 20:44 TravisCI.changes
>> -rw-r--r-- 1 jakob jakob 54393712 Mär 23 20:44 TravisCI.image
>> -rwxrwxrwx 1 jakob jakob       79 Mär 23 20:39 vm
>>
>> If I should send any files, please tell me.
>>
>> Note that this is on Windows Subsystem for Linux, but it didn't make
>> any difference in the past.
>> The smalltalkCI output is the same as on Travis: (see below).
>>
>> During the headful run, I could watch it recompiling all methods
>> (presumably after switching Sista on?), and quickly after that Squeak
>> shut down. But I cannot tell whether it did so cleanly or not.
>>
>> Kind regards,
>> Jakob
>>
>>
>> jakob@JAKOBS-PC:~/smalltalkCI$ bin/smalltalkci --headful
>> /mnt/c/Squeak/MA/Squot-Squit/.smalltalk.ston
>>  1) Squeak64-trunk      15) Pharo64-8.0         29) GemStone64-3.4.3
>>  2) Squeak64-5.3        16) Pharo64-7.0         30) GemStone64-3.3.9
>>  3) Squeak64-5.2        17) Pharo64-6.1         31) GemStone64-3.3.2
>>  4) Squeak64-5.1        18) Pharo64-6.0         32) GemStone64-3.3.0
>>  5) Squeak32-trunk      19) Pharo32-stable      33) GemStone64-3.2.12
>>  6) Squeak32-5.3        20) Pharo32-alpha       34) GemStone64-3.1.0.6
>>  7) Squeak32-5.2        21) Pharo32-9.0         35) Moose64-trunk
>>  8) Squeak32-5.1        22) Pharo32-8.0         36) Moose64-8.0
>>  9) Squeak32-5.0        23) Pharo32-7.0         37) Moose64-7.0
>> 10) Squeak32-4.6        24) Pharo32-6.0         38) Moose32-trunk
>> 11) Squeak32-4.5        25) Pharo32-5.0         39) Moose32-8.0
>> 12) Pharo64-stable      26) Pharo32-4.0         40) Moose32-7.0
>> 13) Pharo64-alpha       27) Pharo32-3.0         41) Moose32-6.1
>> 14) Pharo64-9.0         28) GemStone64-3.5.0    42) Moose32-6.0
>> Choose Smalltalk image: 1
>> Preparing folders...
>> Starting Squeak build...
>> Downloading Squeak64-trunk image...
>>  > Time to run: 6.288s
>> Cog VM Information
>> 5.0-201810190412  Sat Oct 20 08:17:23 UTC 2018 gcc 4.8 [Production
>> Spur 64-bit ITHB VM]
>> CoInterpreter VMMaker.oscog-eem.2461 uuid:
>> b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 20 2018
>> StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid:
>> 0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 20 2018
>> VM: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
>> Date: Thu Oct 18 21:12:21 2018 CommitHash: 15341b57
>> Plugins: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
>> Linux travis-job-7e855ac8-57b9-4f6f-bf30-fd6e0ad67398
>> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017
>> x86_64 x86_64 x86_64 GNU/Linux
>> plugin path: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412
>> [default: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412/]
>>  > Time to run: 0.061s
>> Preparing Squeak64-trunk image for CI...
>> ........................................................Error:
>> vmParameterAt:put: failed > Time to run: 275.810s
>> Build was unable to report intermediate build status.
>> cat: /home/jakob/smalltalkCI/_builds/2020_03_23_20_39_33/build_status.txt:
>> Datei oder Verzeichnis nicht gefunden
>>
>> Error with status code 1:
>> 237 check_and_consume_build_status_file /home/jakob/smalltalkCI/helpers.sh
>>
>



Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

fniephaus
Hi all,

smalltalkCI uses the same set of VMs across all Squeak builds. Maybe
this should change at some point, but at least we need to upgrade the
set of VMs soon. I'll take care of it soon and let you know...

Fabio

On Mon, Mar 23, 2020 at 10:09 PM Nicolas Cellier
<[hidden email]> wrote:

>
>
>
> Le lun. 23 mars 2020 à 21:12, Jakob Reschke <[hidden email]> a écrit :
>>
>> The VMs are pulled by smalltalkCI, I have no control over that. Or have I?
>>
> Maybe check the smalltalkCI scripts and send a pull request (or simply open an issue: Squeak32/64-trunk and 5.3 should use VM from 2020).
>
>> Also note that this is a Linux Squeak VM, running under the Linux
>> subsystem, not a Windows Squeak VM.
>>
> Ah yes, sorry,
> I also compile and test spur64 on wsl from time to time, so should better reconnect my mind ;)
> Let me see, introduction of wheel events support is from Nov 2018
> https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/897ef1725e32c2eb3d24e3402b2e95b114b8b28b
>
> So VM 5.0-201810190412 is still too old on linux too, not only on windows.
>
>> Am Mo., 23. März 2020 um 21:07 Uhr schrieb Nicolas Cellier
>> <[hidden email]>:
>> >
>> > Hi Jakob,
>> > I think that I put in 6.0 trunk a postscript instruction that activates the delivery of mouse wheel events.
>> > This requires an updated VM on windows (I honoured this request by end of 2019).
>> > So the question is why is the VM so old?
>> >
>> > Le lun. 23 mars 2020 à 20:59, Jakob Reschke <[hidden email]> a écrit :
>> >>
>> >> Am Di., 10. März 2020 um 20:47 Uhr schrieb Jakob Reschke
>> >> <[hidden email]>:
>> >> >
>> >> > Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
>> >> > <[hidden email]>:
>> >> > >
>> >> > > Any stack traces?  Which parameter, which value was being assigned, etc?
>> >> > >
>> >> > > "Something went wrong" is rather vague...
>> >> >
>> >> > I know, unfortunately Travis does not provide any more specific output. :-(
>> >> > Maybe I can try to run smalltalkCI on my machine later and see whether
>> >> > that gives anything.
>> >>
>> >> I finally got around to try a local build. But still no debug log or
>> >> crash dump to be found.
>> >> The Trunk builds are still failing, while the 5.2 builds are fine.
>> >>
>> >> @Fabio: should I look anywhere else than in the build directory? This
>> >> is the listing:
>> >>
>> >> jakob@JAKOBS-PC:~/smalltalkCI/_builds/2020_03_23_20_39_33$ ls -la
>> >> insgesamt 135648
>> >> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:44 .
>> >> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:39 ..
>> >> -rw-rw-rw- 1 jakob jakob      496 Mär 23 20:39 coveralls_build_data.json
>> >> -rw-rw-rw- 1 jakob jakob      390 Mär 23 20:44 load.st
>> >> drwxrwxrwx 1 jakob jakob     4096 Mär 23 20:43 package-cache
>> >> -rw-rw-rw- 1 jakob jakob     1961 Mär 23 20:39 prepare.st
>> >> -rw-r--r-- 1 jakob jakob      120 Dez  6  2018
>> >> ._Squeak5.3alpha-18294-64bit.changes
>> >> -rw-r--r-- 1 jakob jakob      268 Dez  6  2018
>> >> ._Squeak5.3alpha-18294-64bit.image
>> >> -rw-rw-rw- 1 jakob jakob 26874889 Mär 23 20:39 Squeak64-trunk.tar.gz
>> >> -rw-r--r-- 1 jakob jakob      212 Okt  8  2018 ._SqueakV50.sources
>> >> -rw-r--r-- 1 jakob jakob 35184983 Okt  8  2018 SqueakV50.sources
>> >> -rw-r--r-- 1 jakob jakob 20592231 Mär 23 20:44 TravisCI.changes
>> >> -rw-r--r-- 1 jakob jakob 54393712 Mär 23 20:44 TravisCI.image
>> >> -rwxrwxrwx 1 jakob jakob       79 Mär 23 20:39 vm
>> >>
>> >> If I should send any files, please tell me.
>> >>
>> >> Note that this is on Windows Subsystem for Linux, but it didn't make
>> >> any difference in the past.
>> >> The smalltalkCI output is the same as on Travis: (see below).
>> >>
>> >> During the headful run, I could watch it recompiling all methods
>> >> (presumably after switching Sista on?), and quickly after that Squeak
>> >> shut down. But I cannot tell whether it did so cleanly or not.
>> >>
>> >> Kind regards,
>> >> Jakob
>> >>
>> >>
>> >> jakob@JAKOBS-PC:~/smalltalkCI$ bin/smalltalkci --headful
>> >> /mnt/c/Squeak/MA/Squot-Squit/.smalltalk.ston
>> >>  1) Squeak64-trunk      15) Pharo64-8.0         29) GemStone64-3.4.3
>> >>  2) Squeak64-5.3        16) Pharo64-7.0         30) GemStone64-3.3.9
>> >>  3) Squeak64-5.2        17) Pharo64-6.1         31) GemStone64-3.3.2
>> >>  4) Squeak64-5.1        18) Pharo64-6.0         32) GemStone64-3.3.0
>> >>  5) Squeak32-trunk      19) Pharo32-stable      33) GemStone64-3.2.12
>> >>  6) Squeak32-5.3        20) Pharo32-alpha       34) GemStone64-3.1.0.6
>> >>  7) Squeak32-5.2        21) Pharo32-9.0         35) Moose64-trunk
>> >>  8) Squeak32-5.1        22) Pharo32-8.0         36) Moose64-8.0
>> >>  9) Squeak32-5.0        23) Pharo32-7.0         37) Moose64-7.0
>> >> 10) Squeak32-4.6        24) Pharo32-6.0         38) Moose32-trunk
>> >> 11) Squeak32-4.5        25) Pharo32-5.0         39) Moose32-8.0
>> >> 12) Pharo64-stable      26) Pharo32-4.0         40) Moose32-7.0
>> >> 13) Pharo64-alpha       27) Pharo32-3.0         41) Moose32-6.1
>> >> 14) Pharo64-9.0         28) GemStone64-3.5.0    42) Moose32-6.0
>> >> Choose Smalltalk image: 1
>> >> Preparing folders...
>> >> Starting Squeak build...
>> >> Downloading Squeak64-trunk image...
>> >>  > Time to run: 6.288s
>> >> Cog VM Information
>> >> 5.0-201810190412  Sat Oct 20 08:17:23 UTC 2018 gcc 4.8 [Production
>> >> Spur 64-bit ITHB VM]
>> >> CoInterpreter VMMaker.oscog-eem.2461 uuid:
>> >> b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 20 2018
>> >> StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid:
>> >> 0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 20 2018
>> >> VM: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
>> >> Date: Thu Oct 18 21:12:21 2018 CommitHash: 15341b57
>> >> Plugins: 201810190412 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
>> >> Linux travis-job-7e855ac8-57b9-4f6f-bf30-fd6e0ad67398
>> >> 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017
>> >> x86_64 x86_64 x86_64 GNU/Linux
>> >> plugin path: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412
>> >> [default: /home/jakob/smalltalkCI/_cache/vms/Squeak64-trunk/sqcogspur64linux/lib/squeak/5.0-201810190412/]
>> >>  > Time to run: 0.061s
>> >> Preparing Squeak64-trunk image for CI...
>> >> ........................................................Error:
>> >> vmParameterAt:put: failed > Time to run: 275.810s
>> >> Build was unable to report intermediate build status.
>> >> cat: /home/jakob/smalltalkCI/_builds/2020_03_23_20_39_33/build_status.txt:
>> >> Datei oder Verzeichnis nicht gefunden
>> >>
>> >> Error with status code 1:
>> >> 237 check_and_consume_build_status_file /home/jakob/smalltalkCI/helpers.sh
>> >>
>> >
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Jakob Reschke-2
Am Mo., 23. März 2020 um 22:17 Uhr schrieb Fabio Niephaus <[hidden email]>:
>
> smalltalkCI uses the same set of VMs across all Squeak builds. Maybe
> this should change at some point, but at least we need to upgrade the
> set of VMs soon. I'll take care of it soon and let you know...

Thank you :-)
Is the process what needs to be done described somewhere?

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

fniephaus
On Mon, Mar 23, 2020 at 10:20 PM Jakob Reschke <[hidden email]> wrote:
>
> Am Mo., 23. März 2020 um 22:17 Uhr schrieb Fabio Niephaus <[hidden email]>:
> >
> > smalltalkCI uses the same set of VMs across all Squeak builds. Maybe
> > this should change at some point, but at least we need to upgrade the
> > set of VMs soon. I'll take care of it soon and let you know...
>
> Thank you :-)
> Is the process what needs to be done described somewhere?

No, not really. But the source is at [1], the VMs are hosted on GitHub [2].

Fabio

[1] https://github.com/hpi-swa/smalltalkCI/blob/13fd88bfd4940a112df245195bca2837093944ce/squeak/run.sh#L143
[2] https://github.com/hpi-swa/smalltalkCI/releases/tag/v2.8.4

>

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

fniephaus
Here you go: https://github.com/hpi-swa/smalltalkCI/commit/e057947e56e52eb522379b21c64ffac961dcf533

@Jakob: Please restart your builds and let me know if this fixes the issue on your end.

Cheers,
Fabio


On Mon, Mar 23, 2020 at 10:24 PM Fabio Niephaus <[hidden email]> wrote:
On Mon, Mar 23, 2020 at 10:20 PM Jakob Reschke <[hidden email]> wrote:
>
> Am Mo., 23. März 2020 um 22:17 Uhr schrieb Fabio Niephaus <[hidden email]>:
> >
> > smalltalkCI uses the same set of VMs across all Squeak builds. Maybe
> > this should change at some point, but at least we need to upgrade the
> > set of VMs soon. I'll take care of it soon and let you know...
>
> Thank you :-)
> Is the process what needs to be done described somewhere?

No, not really. But the source is at [1], the VMs are hosted on GitHub [2].

Fabio

[1] https://github.com/hpi-swa/smalltalkCI/blob/13fd88bfd4940a112df245195bca2837093944ce/squeak/run.sh#L143
[2] https://github.com/hpi-swa/smalltalkCI/releases/tag/v2.8.4

>


Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

Jakob Reschke-2
That fixed the setup phase, thank you again!

Now the same builds are red because of ModificationForbidden. But that
is something I must worry about.

Note that it halted the build instead of just failing the affected
test cases, should it be that way?


Am Do., 26. März 2020 um 11:23 Uhr schrieb Fabio Niephaus <[hidden email]>:

>
> Here you go: https://github.com/hpi-swa/smalltalkCI/commit/e057947e56e52eb522379b21c64ffac961dcf533
>
> @Jakob: Please restart your builds and let me know if this fixes the issue on your end.
>
> Cheers,
> Fabio
>
>
> On Mon, Mar 23, 2020 at 10:24 PM Fabio Niephaus <[hidden email]> wrote:
>>
>> On Mon, Mar 23, 2020 at 10:20 PM Jakob Reschke <[hidden email]> wrote:
>> >
>> > Am Mo., 23. März 2020 um 22:17 Uhr schrieb Fabio Niephaus <[hidden email]>:
>> > >
>> > > smalltalkCI uses the same set of VMs across all Squeak builds. Maybe
>> > > this should change at some point, but at least we need to upgrade the
>> > > set of VMs soon. I'll take care of it soon and let you know...
>> >
>> > Thank you :-)
>> > Is the process what needs to be done described somewhere?
>>
>> No, not really. But the source is at [1], the VMs are hosted on GitHub [2].
>>
>> Fabio
>>
>> [1] https://github.com/hpi-swa/smalltalkCI/blob/13fd88bfd4940a112df245195bca2837093944ce/squeak/run.sh#L143
>> [2] https://github.com/hpi-swa/smalltalkCI/releases/tag/v2.8.4
>>
>> >
>
>

Reply | Threaded
Open this post in threaded view
|

Re: smalltalkCI Trunk broken: vmParameterAt:put: failed

fniephaus
On Thu, Mar 26, 2020 at 11:10 PM Jakob Reschke <[hidden email]> wrote:
That fixed the setup phase, thank you again!

Now the same builds are red because of ModificationForbidden. But that
is something I must worry about.

Note that it halted the build instead of just failing the affected
test cases, should it be that way?

This might also be the reason why 64bit trunk is currently broken:

Are immutable literals limited to 64bit or why doesn't this seem to affect 32bit?

Fabio
 


Am Do., 26. März 2020 um 11:23 Uhr schrieb Fabio Niephaus <[hidden email]>:
>
> Here you go: https://github.com/hpi-swa/smalltalkCI/commit/e057947e56e52eb522379b21c64ffac961dcf533
>
> @Jakob: Please restart your builds and let me know if this fixes the issue on your end.
>
> Cheers,
> Fabio
>
>
> On Mon, Mar 23, 2020 at 10:24 PM Fabio Niephaus <[hidden email]> wrote:
>>
>> On Mon, Mar 23, 2020 at 10:20 PM Jakob Reschke <[hidden email]> wrote:
>> >
>> > Am Mo., 23. März 2020 um 22:17 Uhr schrieb Fabio Niephaus <[hidden email]>:
>> > >
>> > > smalltalkCI uses the same set of VMs across all Squeak builds. Maybe
>> > > this should change at some point, but at least we need to upgrade the
>> > > set of VMs soon. I'll take care of it soon and let you know...
>> >
>> > Thank you :-)
>> > Is the process what needs to be done described somewhere?
>>
>> No, not really. But the source is at [1], the VMs are hosted on GitHub [2].
>>
>> Fabio
>>
>> [1] https://github.com/hpi-swa/smalltalkCI/blob/13fd88bfd4940a112df245195bca2837093944ce/squeak/run.sh#L143
>> [2] https://github.com/hpi-swa/smalltalkCI/releases/tag/v2.8.4
>>
>> >
>
>



12