-
Notifications
You must be signed in to change notification settings - Fork 4
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
watch is confusing #129
Comments
@jellevandenhooff! thanks for trying run. Great catch! This is only semi-intended behavior: it works as designed, but it's a bad design. What's happening is that even though the ui is "tui", the run as-a-whole is getting marked as "short", and the execution stuff exits when the last task completes. I'm working on a refactor that makes the long-vs-short behavior a lot more explicit; I'll include this as a test case. In the meantime, your workaround seems like a good option. |
this test is now passing in my dev branch, so this enhancement will definitely happen some time. |
Hi! Thank you for your delightful software.
I tried the following
tasks.toml
.I ran
run -ui=tui go-test
. This ran my tests.Then I went and changed a go file and expected the tests would run again. The tests did not run again, even though
@watch
claiming to be watching**/*.go
.Eventually I figured out that running a long
dev
task depending ongo-test
fixed the re-runner. Is this behavior intended?The text was updated successfully, but these errors were encountered: