Opened 8 years ago
Closed 7 years ago
#14127 closed defect (fixed)
builder fails silently (exit code is still 0)
Reported by: | liucougar | Owned by: | Rawld Gill |
---|---|---|---|
Priority: | high | Milestone: | 1.8 |
Component: | BuildSystem | Version: | 1.7.0b1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
add the following line into a js file, make sure that file is built by builder
s.replace(/[-\\/.+()|]/g, function(x){ return "\\" + x; });
build will fail with the following error:
{ stack: [Getter/Setter], arguments: undefined, type: undefined, message: 'Socket is not writable' } Error: Socket is not writable at Socket._writeOut (net.js:391:11) at Socket.write (net.js:377:17) at Object.write (build/transforms/writeOptimized:177:21) at build/transforms/writeOptimized:131:29 at build/transforms/writeOptimized:274:5 at Array.0 (build/transforms/writeOptimized:282:11) at build/main:128:23 at build/main:107:5 at build/transforms/writeAmd:178:5 at build/node/fs:23:9
but it does not actually specify what's the problem (I had to add the following line into runner.stderr.on("data", function(data){
:
console.error('-------------- '+data);
the build definitely fails, but the exit code is still 0
Change History (5)
comment:1 Changed 8 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 8 years ago by
Status: | new → assigned |
---|
comment:3 Changed 8 years ago by
Note: See
TracTickets for help on using
tickets.
Builder also does not return a non-zero exit code when the optimizer reports errors, even though the number of errors is logged and available.