In fact, this integration step ( https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z <https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label...>) was already passed by Epicea in December. That was before spur, it might be related to spur. That time, the integration of Epicea revealed a bug in delay's scheduling... maybe now it's revealing some bug in Windows+spur...? Martin On Fri, Feb 5, 2016 at 10:09 AM, Blondeau Vincent < vincent.blondeau@worldline.com> wrote:
If you remove any line, it stops crashingâ¦
I really donât know what is going onâ¦
Vincent
*De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part de* Henrik Nergaard *Envoyé :* vendredi 5 février 2016 14:03
*Ã :* Pharo Development List *Objet :* Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)
Removing
#(IRPrinterV2 #(visitStoreTemp: visitStoreRemoteTemp: visitPopIntoLiteralVariable: visitPushTemp: visitReturnLiteral: visitStoreInstVar: visitStoreLiteralVariable: visitPushLiteralVariable: visitPushInstVar: visitJump: visitPushLiteral: label: visitPushArray: visitPopIntoTemp: visitReturnInstVar: visitPopIntoRemoteTemp: visitTempVector: visitJumpIf: visitPushRemoteTemp: visitPopIntoInstVar: visitSend: ))
And it stops crashing.
- BTW, there is not crash.dmp, does it works with spur?
https://pharo.fogbugz.com/f/cases/17506/when-an-Image-crashes-a-crash-dmp-fi...
Best regards,
Henrik
*From:* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <pharo-dev-bounces@lists.pharo.org>] *On Behalf Of *Blondeau Vincent *Sent:* Friday, February 5, 2016 1:54 PM *To:* Pharo Development List <pharo-dev@lists.pharo.org> *Subject:* Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)
Very strange bug indeed that happens on windows machines that crashes the VM. I succeeded to reduce the problem to an evaluation of a collectionâ¦
Can someone have the same issue under Windows or Mac?
To reproduce : Copy paste the contents of the attached file in the playground and print it or do it
It works on pre-spur vm.
BTW, there is not crash.dmp, does it works with spur?
Vincent
*De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <pharo-dev-bounces@lists.pharo.org>] *De la part de* Marcus Denker *Envoyé :* vendredi 5 février 2016 13:01 *à :* Pharo Development List *Objet :* Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)
On 05 Feb 2016, at 12:40, Marcus Denker <marcus.denker@inria.fr> wrote:
I will try do integrate it nowâ¦
No, it still fails.
https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label...
The last test it executed seems to be this:
running suite: Refactoring-Tests-Environment
starting testcase: RBBrowserEnvironmentTest>>testAndEnvironment ...
Very strange...
Marcus
------------------------------
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.
------------------------------
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.