Does Hardware Configuration and Processor Load Impact Software Fault Observability? Raza Abbas Syed1, Brian Robinson2, Laurie Williams1 1Department of Computer Science, North Carolina State University, Raleigh, NC 27695-8206 {rsyed, lawilli3}@ncsu.edu 2ABB Inc., US Corporate Research, Raleigh, NC 27606
[email protected] Abstract. Intermittent failures and nondeterministic behavior test teams during the product development cycle. For failures complicate and compromise the effectiveness of software detected in test, it is difficult to determine the underlying testing and debugging. To increase the observability of fault when reproducing the failure is not possible. When the software faults, we explore the effect hardware configurations underlying fault cannot be determined, the failure report is and processor load have on intermittent failures and the often closed and no additional effort is spent on it until nondeterministic behavior of software systems. We conducted additional occurrences are detected. For faults detected in the a case study on Mozilla Firefox with a selected set of reported field, developers spent considerable effort in either remotely field failures. We replicated the conditions that caused the debugging the fault or traveling to the customer site itself to reported failures ten times on each of nine hardware determine the fault and fix it. configurations by varying processor speed, memory, hard Nondeterministic behavior in software systems can be drive capacity, and processor load. Using several observability tools, we found that hardware configurations that had less attributed to a number of sources. Testers may not have processor speed and memory observed more failures than enough visibility or control over all of the inputs to the others.