Activity
From 05/07/2016 to 06/05/2016
05/17/2016
- 08:13 AM Bug #3112 (Closed): missing import with current-value() stmt
- Task branch 3112a was merged to trunk as revision 11031. 3112a was archived.
- 07:18 AM Bug #3112: missing import with current-value() stmt
- Conversion regression testing has passed.
05/16/2016
- 05:13 PM Bug #3112: missing import with current-value() stmt
- The following program will fail to build because of a missing import:...
- 05:08 PM Bug #3112 (Closed): missing import with current-value() stmt
05/12/2016
- 04:55 PM Bug #3102 (Closed): P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- 04:53 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Branch @3102a@ was merged to trunk as revno @11026@ then it was archived.
- 04:41 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Eric reports that the ETF batch tests (where this problem occurred) have successfully executed and the problem is gon...
- 02:50 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Testing completed, no regressions. The results - @3102a_11026_6c4b2ca_20160512_evl.zip@.
- 11:46 AM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- The main part completed without regressions. Running the @CTRL-C@ part.
05/11/2016
- 04:07 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Greg Shah wrote:
> While Eric is testing this on the ETF, please go ahead and test this in MAJIC runtime regression ... - 04:05 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Code Review Task Branch 3102a Revision 11026
I'm fine with the changes.
While Eric is testing this on the ETF, ... - 02:57 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Eugenie Lyzenko wrote:
> The change is from note #7. Eric, is it possible to test it against the issue?
I don't kno... - 02:40 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Task branch @3102a@ for review updated to revision @11026@.
The change is from note #7. Eric, is it possible to te... - 02:18 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Created task branch @3102a@ from trunk revision @11025@.
- 02:04 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Please put it in 3102a.
- 01:42 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- I know this is not good idea to mix several task into one. But due to urgency of this failure I can add the change in...
- 12:39 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- > It's not binary, just a text file. tdump is just the default extension VisualVM assigned when I saved it.
In the... - 12:06 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- I think we getting into loop when @res == -1@(no child process exists) because we suppressed the @stop/continue@ sign...
- 11:47 AM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Greg Shah wrote:
> > No, the Java client had no child processes.
>
> It had one at one time otherwise we wouldn't... - 11:18 AM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- > No, the Java client had no child processes.
It had one at one time otherwise we wouldn't be looping in the @pseu... - 11:10 AM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Eugenie Lyzenko wrote:
> 1. Can you tell what command/program is launching inside child session?
No, the Java clien... - 10:52 AM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- The problem is most likely with the newly added looping around the @waitpid()@ call. I suspect we are missing an exi...
05/10/2016
- 06:55 PM Bug #3102: P2J client consumes all CPU in pseudoTerminalWait across multiple threads
- Eric,
1. Can you tell what command/program is launching inside child session?
2. Can the issue be reproduced perm...
Also available in: Atom