forge
/
build.sh
3
2
Fork 1
Code Issues 6 Pull Requests Releases Wiki Activity

Tracking task progress and error #10

New Issue
Closed
opened 2020-04-24 19:36:59 +00:00 by southerntofu · 1 comment
southerntofu commented 2020-04-24 19:36:59 +00:00
Owner
Copy Link

Maybe instead of exiting early after running backgound tasks, we could track them through lockfiles

this could enable tasks to timeout after a while, for instance. And to display the STDERR of failed tasks, along with a summary of which tasks failed

Maybe instead of exiting early after running backgound tasks, we could track them through lockfiles this could enable tasks to timeout after a while, for instance. And to display the STDERR of failed tasks, along with a summary of which tasks failed
southerntofu commented 2020-09-22 13:19:26 +00:00
Author
Owner
Copy Link

Parallel support was dropped for the moment (pending specification)

Parallel support was dropped for the moment (pending specification)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: forge/build.sh#10
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?