PP-516: Direct write of job's stdout/err files

[scc]

Hi @nithinj,

@nithinj

In the current proposal, -koe does not have any meaning when used along with -Wsandbox=PRIVATE because I believe the similar effect can be obtained by using -Roe. -Wsandbox=PRIVATE used with and without -koe is the same.

Using “-Wsandbox=PRIVATE -Roe” would result in different behavior from the currently documented “-Wsandbox=PRIVATE -koe” if the job fails, since in the -Roe case we’d only remove the file(s) if the job succeeded.

@nithinj

The only question is, do we need to preserve the meaning of -koe with sandbox? This is not required if it does not harm the users(as we are providing an alternative). Please share your views.

I guess I just don’t see a real reason to bother changing the currently documented “-Wsandbox=PRIVATE -koe” behavior, because as it provides behavior (albeit not commonly used) that is not exactly matched by any new functionality, and is consistent with the various definitions of the attributes involved. Does getting rid of the current behavior make implementing and/or maintaining this new feature substantially easier?