I have to admit i found this quite frustrating.
I've written a set of programs that do nightly builds that feed into nightly tests, blah, blah.
One of the requirements is that we bundle our own version of perl with the software, so, every night, perl gets
After time, perl's make test failed in 't/op/fork.t'. The next night it worked thou.
After receiving a query about the unexpected build failure from the local sys. admin. team, i did a bad thing and decided that if fork was failing and then started working again, this could indicate a hardware issue.
Sorry!!! it could also indicate that 't/op/fork.t' is actually testing the rand() functionality.
't/op/fork.t' doesn't do anything at all with srand before forking a calling rand in each new process.
The test depends on the rand() in each process producing different results
Not surprisingly, 't/op/fork.t' fails fairly regularly.