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

cmd/test: Calling this on long-running jobs causes commands to time out thereafter #284

Closed
dshearer opened this issue May 10, 2020 · 0 comments · Fixed by #292
Closed

cmd/test: Calling this on long-running jobs causes commands to time out thereafter #284

dshearer opened this issue May 10, 2020 · 0 comments · Fixed by #292
Assignees
@dshearer
Labels
bug
Milestone
1.4.3

Comments

@dshearer
Copy link
Owner

No description provided.

@dshearer dshearer added the bug label May 10, 2020
@dshearer dshearer self-assigned this May 10, 2020
@dshearer dshearer added this to the 1.4.3 milestone May 24, 2020
dshearer added a commit that referenced this issue May 25, 2020
@dshearer
(#284) Fix "test" command for long-running jobs
c7be15a 
We now use a separte Unix socket to stream the job's output
as it runs.

Unfortunately, we must drop support for this command via TCP.
@dshearer dshearer mentioned this issue May 25, 2020
Merged
dshearer added a commit that referenced this issue May 25, 2020
@dshearer
(#284) Fix "test" command for long-running jobs
3ed75df 
We now use a separte Unix socket to stream the job's output
as it runs.

Unfortunately, we must drop support for this command via TCP.
@dshearer dshearer mentioned this issue May 25, 2020
Closed
@dshearer dshearer changed the title Calling cat command on long-running jobs causes jobberrunner to become unresponsive Calling test command on long-running jobs causes jobberrunner to become unresponsive May 25, 2020
@dshearer dshearer changed the title Calling test command on long-running jobs causes jobberrunner to become unresponsive Calling test command on long-running jobs causes commands to become unresponsive thereafter May 25, 2020
@dshearer dshearer changed the title Calling test command on long-running jobs causes commands to become unresponsive thereafter Calling test command on long-running jobs causes commands to time out thereafter May 25, 2020
@dshearer dshearer changed the title Calling test command on long-running jobs causes commands to time out thereafter cmd/test: Calling this on long-running jobs causes commands to time out thereafter May 25, 2020
dshearer added a commit that referenced this issue May 26, 2020
@dshearer
(#284) Fix "test" command for long-running jobs
3549306 
We now use a separte Unix socket to stream the job's output
as it runs.

Unfortunately, we must drop support for this command via TCP.
dshearer added a commit that referenced this issue May 26, 2020
@dshearer
(#284) Fix "test" command for long-running jobs
f702562 
We now use a separte Unix socket to stream the job's output
as it runs.

Unfortunately, we must drop support for this command via TCP.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dshearer dshearer

Labels
bug
Projects
None yet
Milestone
1.4.3
Development

Successfully merging a pull request may close this issue.

(#284) Fix "test" command for long-running jobs dshearer/jobber
1 participant
@dshearer