Closed Bug 106272 Opened 23 years ago Closed 19 years ago

No error checking for chdir, mkdir and getcwd commands

Categories

(CCK Graveyard :: CCK-General, defect, P2)

Product:
CCK Graveyard
Component:
CCK-General
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: shrutiv, Assigned: shrutiv)

Details

(Whiteboard: Cecko) 

Include errror checks for the above commands.
qa to blee
QA Contact: barrettl → blee
Status: NEW → ASSIGNED
Priority: -- → P2
For the wizard, we could display the error in a message box when it happens. 

For the install builder, we could write the error message to stdout so that
command line users will see them, as well as writing them to a log file. Then,
when CCK calls install builder, it should check the log for errors and display
them since the wizard user won't see stdout.
and I assume we should abort the build when these errors occur because we cannot
successfully proceed.  Correct?
> and I assume we should abort the build when these errors occur
If we are aborting the build when these errors occur, then do we need to have a
log file? 

Adding Cecko to status whiteboard.
Whiteboard: Cecko
out for rtm.
Old CCK.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.