Le 30/11/2014 01:13, Jussi Lahtinen a écrit :
Nothing happens there after having run the test an hundred times.
Can you try revision #6686 and tell me if it changes anything?
Sorry to tell but something is still not right. But things are already
better, GUI version works perfectly, but
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
I think with latest microcode... I'll check later.
Jussi
On Sun, Nov 30, 2014 at 2:25 PM, Benoît Minisini
gam...@users.sourceforge.net wrote:
Le 30/11/2014 01:13, Jussi Lahtinen a écrit :
Nothing happens there after having run the test
Le 30/11/2014 13:37, Jussi Lahtinen a écrit :
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
I think with latest microcode... I'll check later.
Jussi
I have tested 100x times on my own 64 bits system, and in a 32 bits VM
running ArchLinux. No problem...
Are you sure that you have
Le 30/11/2014 15:50, Benoît Minisini a écrit :
Le 30/11/2014 13:37, Jussi Lahtinen a écrit :
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
I think with latest microcode... I'll check later.
Jussi
I have tested 100x times on my own 64 bits system, and in a 32 bits VM
running ArchLinux.
Le 30/11/2014 16:41, Benoît Minisini a écrit :
Le 30/11/2014 15:50, Benoît Minisini a écrit :
Le 30/11/2014 13:37, Jussi Lahtinen a écrit :
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
I think with latest microcode... I'll check later.
Jussi
I have tested 100x times on my own 64 bits
OK, I finally got one error (but 239), even if I replaced Wait 0.1 by
hProcess.Wait. Let's go back investigating...
I'll make the change in the code. Good to see it's not fault in my system.
Jussi
--
Download BIRT
Le 30/11/2014 19:10, Jussi Lahtinen a écrit :
OK, I finally got one error (but 239), even if I replaced Wait 0.1 by
hProcess.Wait. Let's go back investigating...
I'll make the change in the code. Good to see it's not fault in my system.
Jussi
At the moment I can get the 239 error, i.e.
At the moment I can get the 239 error, i.e. when running 'echo test'
through a virtual terminal.
In Linux, you have a system call that tells you how many bytes can be
read on a file descriptor: ioctl(fd, FIONREAD, ...), and a system call
(select) that tells you when something can be read on
I tested if this happens also with cat and it didn't make any difference.
Here is GambasTester with improved test (they are just inside loop).
Much easier to demonstrate the problem.
Jussi
GambasTestercmd-0.9.30.tar.gz
Description: GNU Zip compressed data
Le 28/11/2014 23:30, Jussi Lahtinen a écrit :
Now something else happens... again with command line version.
mTest.Process_Read.1623: #47: Read error
mTest.DoTests.1543 mTest.Main.1832
Jussi
Nothing happens there after having run the test an hundred times.
Can you try revision #6686 and
Nothing happens there after having run the test an hundred times.
Can you try revision #6686 and tell me if it changes anything?
Sorry to tell but something is still not right. But things are already
better, GUI version works perfectly, but command-line version reported
error after 40 runs.
Nothing happens there after having run the test an hundred times.
Can you try revision #6686 and tell me if it changes anything?
Sorry to tell but something is still not right. But things are already
better, GUI version works perfectly, but command-line version reported
error after 40
Le 28/11/2014 02:54, Jussi Lahtinen a écrit :
Did you recompile your project entirely before running it?
Yes, and now twice. I deleted my trunk folder, checked it out again.
Uninstalled Gambas entirely from my system and recompiled it.
Same result.
Jussi
Can you try revision #6683?
I
Now something else happens... again with command line version.
mTest.Process_Read.1623: #47: Read error
mTest.DoTests.1543 mTest.Main.1832
Jussi
On Fri, Nov 28, 2014 at 10:15 PM, Benoît Minisini
gam...@users.sourceforge.net wrote:
Le 28/11/2014 02:54, Jussi Lahtinen a écrit :
Did you
Le 23/11/2014 17:32, Jussi Lahtinen a écrit :
With latest revision (6670) my GambasTester crashes randomly when run from
terminal.
1. Unpack attached project into some folder, and open terminal to it.
2. gbc3 -ag
3. run gbx3 several times.
mTest.Process_Read.1616: #13: Null object
It
The bug has been fixed in revision #6681: the SHELL or EXEC command
could sometimes raise the Read event before its return value has been
assigned.
GUI version of GambasTester passes without errors (tested 20 times).
But command-line version doesn't (the project attached). Test 239 (exec
Le 28/11/2014 01:34, Jussi Lahtinen a écrit :
The bug has been fixed in revision #6681: the SHELL or EXEC command
could sometimes raise the Read event before its return value has been
assigned.
GUI version of GambasTester passes without errors (tested 20 times).
But command-line version
Did you recompile your project entirely before running it?
Yes, and now twice. I deleted my trunk folder, checked it out again.
Uninstalled Gambas entirely from my system and recompiled it.
Same result.
Jussi
--
I did more testing with latest revision (6679).
I made pure command-line version of the tester and I do not get the crash.
However I get random failing of the test. Sometimes the string is not
returned, instead null string.
The project is attached. Test 239 is disabled, and test 240 reports always
With latest revision (6670) my GambasTester crashes randomly when run from
terminal.
1. Unpack attached project into some folder, and open terminal to it.
2. gbc3 -ag
3. run gbx3 several times.
mTest.Process_Read.1616: #13: Null object
It seem not to crash when run from IDE.
[System]
Le 23/11/2014 17:32, Jussi Lahtinen a écrit :
With latest revision (6670) my GambasTester crashes randomly when run from
terminal.
1. Unpack attached project into some folder, and open terminal to it.
2. gbc3 -ag
3. run gbx3 several times.
mTest.Process_Read.1616: #13: Null object
It
21 matches
Mail list logo
