Segfault on Moose 6.1 jobs
Hello, I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6). Please find attached the latest failing stack trace. Here are the 2 jobs that fails: https://ci.inria.fr/moose/job/moose-6.1/345/console https://ci.inria.fr/moose/job/moose-6.1/347/console It seems that they are not failing for the same reason. Maybe because the job is not using the latest VM? : pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 Revision: https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply@github.com> Jenkins build #594 Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/] Thanks in advance Cheers, Vincent !!!************************************************************************************* "Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
Hi Vincent, On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent < vincent.blondeau@worldline.com> wrote:
Hello,
I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6).
Please find attached the latest failing stack trace.
Here are the 2 jobs that fails:
https://ci.inria.fr/moose/job/moose-6.1/345/console
https://ci.inria.fr/moose/job/moose-6.1/347/console
It seems that they are not failing for the same reason.
Maybe because the job is not using the latest VM? :
pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM]
Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Yes, this is very old. I suggest you update to something around VMMaker 1776 at the start of November. Right now there is a little instability from the LLP64 work for Win64, otherwise I would recommend the tip.
With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Revision: https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply@github.com> Jenkins build #594
Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/]
Thanks in advance
Cheers,
Vincent
!!!********************************************************* **************************** "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
-- _,,,^..^,,,_ best, Eliot
Thanks Eliot, However, I use this URL to get Pharo vm: http://get.pharo.org/60+vmLatest. The zip file (here: http://files.pharo.org/get-files/60/) was created on October 12, 2016. Did you mean that I do not get the latest one for Pharo60? Vincent De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de Eliot Miranda Envoyé : mercredi 16 novembre 2016 18:41 à : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Segfault on Moose 6.1 jobs Hi Vincent, On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent <vincent.blondeau@worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hello, I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6). Please find attached the latest failing stack trace. Here are the 2 jobs that fails: https://ci.inria.fr/moose/job/moose-6.1/345/console https://ci.inria.fr/moose/job/moose-6.1/347/console It seems that they are not failing for the same reason. Maybe because the job is not using the latest VM? : pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 Yes, this is very old. I suggest you update to something around VMMaker 1776 at the start of November. Right now there is a little instability from the LLP64 work for Win64, otherwise I would recommend the tip. With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 Revision: https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply@github.com<mailto:noreply@github.com>> Jenkins build #594 Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/] Thanks in advance Cheers, Vincent !!!************************************************************************************* "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" -- _,,,^..^,,,_ best, Eliot !!!************************************************************************************* "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
On 17 Nov 2016, at 10:18, Blondeau Vincent <vincent.blondeau@worldline.com> wrote:
Thanks Eliot,
However, I use this URL to get Pharo vm: http://get.pharo.org/60+vmLatest <http://get.pharo.org/60+vmLatest>. The zip file (here: http://files.pharo.org/get-files/60/ <http://files.pharo.org/get-files/60/>) was created on October 12, 2016.
Did you mean that I do not get the latest one for Pharo60?
yes and no. this is the latest VM with the old process, before the merge with opensmalltalk-vm. Iâm finishing the merge process (it was painful), but I still didnât integrate it into the pharo building process. For the moment, you can download ârealâ latest VMs from here: https://bintray.com/estebanlm/pharo-vm/build/201611142324#files <https://bintray.com/estebanlm/pharo-vm/build/201611142324#files> Esteban
Vincent
De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch <mailto:moose-dev-bounces@list.inf.unibe.ch>] De la part de Eliot Miranda Envoyé : mercredi 16 novembre 2016 18:41 à : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Segfault on Moose 6.1 jobs
Hi Vincent,
On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent <vincent.blondeau@worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: Hello,
I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6). Please find attached the latest failing stack trace.
Here are the 2 jobs that fails: https://ci.inria.fr/moose/job/moose-6.1/345/console <https://ci.inria.fr/moose/job/moose-6.1/345/console> https://ci.inria.fr/moose/job/moose-6.1/347/console <https://ci.inria.fr/moose/job/moose-6.1/347/console>
It seems that they are not failing for the same reason.
Maybe because the job is not using the latest VM? :
pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Yes, this is very old. I suggest you update to something around VMMaker 1776 at the start of November. Right now there is a little instability from the LLP64 work for Win64, otherwise I would recommend the tip.
With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 Revision: https://github.com/pharo-project/pharo-vm.git <https://github.com/pharo-project/pharo-vm.git> Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply@github.com <mailto:noreply@github.com>> Jenkins build #594 Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/]
Thanks in advance
Cheers, Vincent
!!!************************************************************************************* "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
-- _,,,^..^,,,_ best, Eliot
!!!************************************************************************************* "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
participants (3)
-
Blondeau Vincent -
Eliot Miranda -
Esteban Lorenzano