Exact(4)
Based on this fact, statistically we have enough evidence to conclude that there is a difference between the concurrency and non-concurrency bug severity distribution.
We analyze the difference between concurrency and non-concurrency bug severity in order to understand if the severity of bugs is differently distributed.
Other factors that favor reopening, according to the authors, include bug severity and geographical distribution of developers participating in the bug.
Several studies have focused on GNOME's bug database (Bugzilla), whose purpose have been: (1) predict the bug severity [40, 42] (2) determine quality of bug reports [2, 69], and (3) determine the efficiency of developers to address issues [44].
Similar(56)
An important first step in improving the reliability of an operating system is to gain insights into why and how the bugs originate, contributions of the different modules to the bugs, their distribution across severities, the different ways in which the bugs may be resolved and the impact of bug severities on their resolution times.
Fig. 9 Concurrency and non-concurrency bugs severity.
On the other hand, we sorted concurrency bugs severity based on their distributions.
Fig. 10 Concurrency bugs severity Table 7 Sorted concurrency bugs severity Rank Severity Most frequent concurrency bug types 1 Blocker – 2 Critical Deadlock (17%) Suspension (21%) 3 Major Atomicity violation (5%) Starvation (6%) Livelock (1%) 4 Minor Data race (59%) Order violation (18%) Atomicity violation (5%) 5 Trival –.
Fig. 11 Fixing time comparison for blocker concurrency and blocker non-concurrency bugs Table 8 Fixing time for the bugs with Blocker severity Fixing time Bug Average Minimum Maximum Median Standard deviation Concurrency 57.4 0.1 2025.0 11.3 206.1 Non-concurrency 54.3 0.1 831.4 8.9 134.1.
We analyze the fixing time of the bug with "Blocker" severity in order to compare the fixing time for the severest concurrency and non-concurrency bugs.
(4) Concurrency and non-concurrency bugs are different in terms of severity, while concurrency bugs are severer than non-concurrency bugs.
Write better and faster with AI suggestions while staying true to your unique style.
Since I tried Ludwig back in 2017, I have been constantly using it in both editing and translation. Ever since, I suggest it to my translators at ProSciEditing.

Justyna Jupowicz-Kozak
CEO of Professional Science Editing for Scientists @ prosciediting.com