Skip to content

Conversation

@khk-globus
Copy link
Collaborator

Description

No functional difference, but make the BSUB commands slightly less redundant, and easier (at least for my brain) to visually parse.

Before:

#BSUB -o /some/long/cwd/path/job.stdout
#BSUB -e /some/long/cwd/path/job.stderr

After:

#BSUB -cwd /some/long/cwd/path
#BSUB -o job.stdout
#BSUB -e job.stderr

Changed Behaviour

none

Type of change

  • Code maintenance/cleanup

No functional difference, but make the BSUB commands slightly less redundant.

Before:

    #BSUB -o /some/long/cwd/path/job.stdout
    #BSUB -e /some/long/cwd/path/job.stderr

After:

    #BSUB -cwd /some/long/cwd/path
    #BSUB -o job.stdout
    #BSUB -e job.stderr
@benclifford
Copy link
Collaborator

what's the cwd otherwise? Some launcher scripts drop stuff into wherever they are run (because in the original cloud model we know very little about the remote filesystem, or perhaps because we don't care) so maybe those are placed somewhere else now?

If so, that's a good thing overall, but it would be nice to at least know that is expected to happen or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants