llnl / llnl/maestrowf

$(LAUNCHER) remains in generated study script when batch type == 'local'

Open
#333 0 comments 0 reactions 1 assignee View on GitHub

@FrankD412 is already working on this.

Since Dec 15, 2020.

bug
Dominant language
Python
Stars
161
Forks
49
PR merge metrics
No merged PRs in 30d

Description

When maestro config has:

batch:
type: local

The $(LAUNCHER) is left in the maestro generated (#!/bin/bash) scripts and there is an error:

LAUNCHER: command not found 

when the script is run.

The script does execute even though bash doesn't like it that LAUNCHER is not defined.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.