Re: Reporting test failures within cron

by davidrw (Prior)

on Sep 13, 2005 at 12:23 UTC ( [id://491559]=note: print w/replies, xml )

Need Help??

Assuming that whatever you're running (i think prove does) uses exit codes on failure, something simple like this would work (bash syntax):

0 3 * * * prove foo.t > /tmp/prove$$ 2>&1 || cat /tmp/prove$$
[download]

And it relies on cron's behavior of emailing you whatever output is generated by a job -- here we're printing the whole output iff it failed..

Comment on Re: Reporting test failures within cron Select or Download Code

Replies are listed 'Best First'.
Re^2: Reporting test failures within cron by Anonymous Monk on Jan 27, 2010 at 17:18 UTC
This works but for security reasons it would be better to do something like: (tmp_file_name=`mktemp`; prove foo.t > "$tmp_file_name" 2>&1 \|\| cat "$tmp_file_name")	[reply]

Domain Nodelet^?

Node Status^?

node history
Node Type: note [id://491559]
help

Chatterbox^?

How do I use this? • Last hour • Other CB clients

Other Users^?

Others making s'mores by the fire in the courtyard of the Monastery: (3)

As of 2024-04-25 22:16 GMT

Sections^?

Information^?

Find Nodes^?

Leftovers^?

Voting Booth^?

No recent polls found