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

task STDERR should also be sent to STDOUT #16

New Issue
Open
opened 2020-04-29 14:41:55 +00:00 by southerntofu · 1 comment
southerntofu commented 2020-04-29 14:41:55 +00:00
Owner
Copy Link

It would be better if STDERR is also redirected to a task's STDOUT by default so that parsing errors can be done from task.err only, while you could see everything from task.log in case you want to know all

It would be better if STDERR is also redirected to a task's STDOUT by default so that parsing errors can be done from task.err only, while you could see everything from task.log in case you want to know all
southerntofu commented 2020-04-29 19:38:36 +00:00
Author
Owner
Copy Link

So it looks like that's gonna require some complex shell tricks. Another option is to log the error code into task.err and log everything into task.log

so we can parse task results for #10

So it looks like that's gonna require some complex shell tricks. Another option is to log the error code into task.err and log everything into task.log so we can parse task results for #10
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#16
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?