Re: [Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-26 Thread Tim Mackinnon
I’ve been able to find out more information about this - and have now got the full filename and error in question: `'C:/Users/sam/Documents/Pharo/images/exercism-test-run-7.0-32bit/pharo-local/iceberg/dionisiydk/StateSpecs/StateSpecs-DSL-PragmaBasedShouldExpressions-Tests.package/SpecOfShouldExpre

Re: [Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-25 Thread Tim Mackinnon
I’ve created - https://github.com/pharo-vcs/iceberg/issues/1204 > On 25 Feb 2019, at 17:12, Tim Mackinnon wrote: > > Just to add some additional notes on this (and I will also file an issue, as > I don’t think one has been submitted, and I don’t think this is fully down to > file path length a

Re: [Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-25 Thread Tim Mackinnon
Just to add some additional notes on this (and I will also file an issue, as I don’t think one has been submitted, and I don’t think this is fully down to file path length alone) - After some more testing, we have also seen the error on Windows 32bit as well (so while easier to get in 64bit, it

Re: [Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-21 Thread Tim Mackinnon
Some interesting thoughts below - but my understanding is these images are being created by Pharo Launcher , so they should be isolated from one another? I also don’t understand why you can load with 32bit (multiple images) but only once with 64bit. Do we load radically different git code with l

Re: [Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-21 Thread Henrik Sperre Johansen
Tim Mackinnon wrote > Hi Ben - while I understand the description below - why would it work the > first time (no errors) and then fail the second time in a fresh image? Are > we really sure its just down to non-determinism of the load process > (possibly - but it seems very suspicious to me). There

Re: [Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-21 Thread Tim Mackinnon
Hi Ben - while I understand the description below - why would it work the first time (no errors) and then fail the second time in a fresh image? Are we really sure its just down to non-determinism of the load process (possibly - but it seems very suspicious to me). There is something more fishy

Re: [Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-21 Thread Ben Coman
On Thu, 21 Feb 2019 at 20:36, Tim Mackinnon wrote: > We noticed a weird problem when testing the pharo exercism project. > > When loading on Windows10 in a fresh 64bit image with the following > evaluate in the playground: > > Metacello new > baseline: 'Exercism'; > repository: 'github://exerci

[Pharo-users] Windows 64bit, long filename issue but after a second load, how to categorise and report this?

2019-02-21 Thread Tim Mackinnon
We noticed a weird problem when testing the pharo exercism project. When loading on Windows10 in a fresh 64bit image with the following evaluate in the playground: Metacello new baseline: 'Exercism'; repository: 'github://exercism/pharo-smalltalk:master/dev/src'; load. The project seemed t