Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

self-run scripts don't generate output or respect CLI arguments #288

Closed
garthk opened this issue Dec 30, 2014 · 4 comments
Assignees
Labels
Milestone

Comments

@garthk
Copy link

@garthk garthk commented Dec 30, 2014

The README documentation for schedule suggests lab 3.x style self-run scripts should work. They do, in that they run the tests and exit with a status code. They don't, in that they don't generate output and ignore command line arguments including --id, --verbose, and --reporter. Both output and options worked in self-run scripts in lab 3.x. Is their omission undocumented, or unintended?

@hueniverse

This comment has been minimized.

Copy link
Member

@hueniverse hueniverse commented Jan 2, 2015

It was never meant to work in the first place. It must have been a side effect. As for what to do now, I'll leave it up to @geek.

@geek geek self-assigned this Jan 2, 2015
@geek geek added question bug and removed question labels Jan 2, 2015
@geek

This comment has been minimized.

Copy link
Member

@geek geek commented Jan 2, 2015

This does seem like a bug. Most likely we should update the readme to be clearer.

@larsenjh

This comment has been minimized.

Copy link

@larsenjh larsenjh commented Feb 24, 2015

The output works fine if you pass in { output: process.stdout } in the first argument of script(). You can basically mimic most of the cli switches with the main config object there.

@geek geek added documentation and removed bug labels Feb 24, 2015
@geek geek removed their assignment Feb 24, 2015
@garthk

This comment has been minimized.

Copy link
Author

@garthk garthk commented Feb 25, 2015

Is there a one-liner to call lab's CLI parsing to get the options argument for script()? From my quick look, lib/cli hides it as internals.options.

@geek geek closed this in #583 May 17, 2016
@geek geek self-assigned this May 17, 2016
@geek geek added this to the 10.5.2 milestone May 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.