09-10-2009
On first run, the program could modify its mtime (or some portion of mtime like microseconds) to some specific value and then on subsequent runs if it sees that mtime quit.
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Can anybody provide me Pointers to Practice tests or any Material to prepare for Brainbench certification in Unix Shell Scripting? Also how good is this Certification for UNIX programmers. Is it worth it? I'm planning to take this certification in 2 weeks. Kindly let me know all the pros... (0 Replies)
Discussion started by: pavan_emani
0 Replies
2. Programming
Dear Gurus,
I have encountered a C question, which I thought of sharing with you.
This question was asked by one of my technical training staff...Though my training was over I'm still thinking of a solution for this..
Write a C program to do a small task(lets say just simply printing a "Hello... (34 Replies)
Discussion started by: vrk1219
34 Replies
3. Shell Programming and Scripting
Hi gurus,
I have done my best to be as precisely as possible with this.
Besides giving the format of file a and file b and the result file
I have also given the algorithm as I have figured out.
I will try to do this and I hope that some of you could help
me to solve this or better yet... (1 Reply)
Discussion started by: ljankok
1 Replies
4. What is on Your Mind?
A global group of scientists are spending the next ten years and a billion dollars to try and develop a computer simulation of the brain:
https://www.humanbrainproject.eu/
I always found it fascinating that the brain can understand itself. This almost sounds like in a few years the computer... (0 Replies)
Discussion started by: figaro
0 Replies
5. Shell Programming and Scripting
G'day,
Here's a teaser for a sed guru, which I surely am not one, as even my
basic sed skills are rusted from years of not practising ... lol
Ok ... we have a string of digits such as:
632413741610252847552619172459483022433027602515212950543016701812771409213148672112
we want it split... (9 Replies)
Discussion started by: naderra
9 Replies
6. What is on Your Mind?
Working on a new cybersecurity, dystopian world series and made a short 2 min teaser today.
Cyber Dystopia (720 HD)
https://www.youtube.com/watch?v=g9Ca07J_YC8
If anyone has any ideas for the story, please write out some story lines in the comments and join the production team! (1 Reply)
Discussion started by: Neo
1 Replies
LEARN ABOUT CENTOS
app::prove::state::result::test
App::Prove::State::Result::Test(3) User Contributed Perl Documentation App::Prove::State::Result::Test(3)
NAME
App::Prove::State::Result::Test - Individual test results.
VERSION
Version 3.28
DESCRIPTION
The "prove" command supports a "--state" option that instructs it to store persistent state across runs. This module encapsulates the
results for a single test.
SYNOPSIS
# Re-run failed tests
$ prove --state=failed,save -rbv
METHODS
Class Methods
"new"
Instance Methods
"name"
The name of the test. Usually a filename.
"elapsed"
The total elapsed times the test took to run, in seconds from the epoch..
"generation"
The number for the "generation" of the test run. The first generation is 1 (one) and subsequent generations are 2, 3, etc.
"last_pass_time"
The last time the test program passed, in seconds from the epoch.
Returns "undef" if the program has never passed.
"last_fail_time"
The last time the test suite failed, in seconds from the epoch.
Returns "undef" if the program has never failed.
"mtime"
Returns the mtime of the test, in seconds from the epoch.
"raw"
Returns a hashref of raw test data, suitable for serialization by YAML.
"result"
Currently, whether or not the test suite passed with no 'problems' (such as TODO passed).
"run_time"
The total time it took for the test to run, in seconds. If "Time::HiRes" is available, it will have finer granularity.
"num_todo"
The number of tests with TODO directives.
"sequence"
The order in which this test was run for the given test suite result.
"total_passes"
The number of times the test has passed.
"total_failures"
The number of times the test has failed.
"parser"
The underlying parser object. This is useful if you need the full information for the test program.
perl v5.16.3 2013-05-02 App::Prove::State::Result::Test(3)