|Hudson console not displaying all of STDOUT [message #903021]
||Tue, 21 August 2012 16:34
| Suu Quan
Registered: August 2012
We -RE build team- use Hudson to start & monitor builds (among other things). The build system existed way before Hudson came within our reach. So, let me explain what we did.|
Our build system starts with 1 generic program that writes its STDOUT+STDERR to a file: log1Start.
Because everything runs in the background, we send everything to a log file.
Then at a certain point, we redirect STDOUT to log2Init (once we know what to build and how to build it). Then, when we actually build, we switch STDOUT to log3Build. At the end, we switch to log4PostBuild.
The intention is to make it easier (for us) to debug when there is problem (smaller log files), and developers are only interested in log3Build when there is compilation-related problems (and test problems).
When we use Hudson, we have Hudson start that program above (as an "Execute Shell command").
Because everything goes to a log file, there is no console output. In order to see progress at the console, we modified the build program to
- before redirecting STDOUT+STDERR to log1Init, we start/fork -in parallel- another program that reads log1Init and displays it to STDOUT. Then it will switch to the other logs in due time.
(We ASSUME that the console displays stdout outputs of the program it invokes.)
PROBLEM: the console stops displaying stdout (from the forked pgm) after a random time. It only displays a portion of the first log (quite large), and stops displaying any lines beyond it.
But it still displays that circular widget to tell that the build is still active. And when the build actually finished, it displays its own final messages.
- Does this ring the bell to any one?
- How does the console behave?
- is there any threshold, limitation for the console to accept outputs? If so, how do I increase that threshold to infinity?
thanks a million
Powered by FUDForum
. Page generated in 0.01683 seconds