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.

Sign up for GitHub

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

Jump to bottom

Repeat last run from IDE gives Scenario still running #71

Closed
sswaroopgupta opened this issue Dec 13, 2017 · 3 comments
Closed

Repeat last run from IDE gives Scenario still running #71

sswaroopgupta opened this issue Dec 13, 2017 · 3 comments
Assignees
@BugDiver
Labels
bug

Comments

@sswaroopgupta
Copy link
Contributor

sswaroopgupta commented Dec 13, 2017 •
edited
Loading

Expected behavior
If an execution is completed. I must be able to repeat the last run

Actual behavior
Path must be string receiving null. Then trying to rerun am Getting Scenario is still running
pathmustbeastring

scenariostillrunning

Steps to replicate

  • LSP tests - run c:\work\getgauge\gauge-lsp-tests\specs\diagnostics\concept diagnostics.spec
  • Now from the js file re-run using the IDE command pallete
  • Getting the above error

Version

Gauge version: 0.9.6.nightly-2017-12-12
Commit Hash: 643882c

Plugins
-------
js (2.0.3.nightly-2017-11-30)

IDE - gauge-0.0.3.nightly-2017-12-08.vsix
@sswaroopgupta sswaroopgupta mentioned this issue Dec 13, 2017
Closed
@sswaroopgupta
Copy link
Contributor Author

Unable to run specs from the IDE after this.

@zabil zabil added the ready label Dec 13, 2017
@BugDiver
Copy link
Member

This issue occurs when running Re-Run failed scenarios from vscode command-palate as well.

BugDiver pushed a commit that referenced this issue Dec 13, 2017
Passing status to display for stop execution #71
e9015df
@BugDiver BugDiver self-assigned this Dec 13, 2017
@BugDiver
Copy link
Member

fix should be available in nightly >= 13-12-2017

@sswaroopgupta sswaroopgupta reopened this Dec 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BugDiver BugDiver

Labels
bug
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zabil @sswaroopgupta @BugDiver