Bug #250
Information collected by kernel backend is not consistent
| Status: | Feedback | Start date: | 04/08/2010 | ||
|---|---|---|---|---|---|
| Priority: | Low | Due date: | 04/14/2010 | ||
| Assignee: | - | % Done: | 50% | ||
| Category: | Backends | Estimated time: | 0.50 hour | ||
| Target version: | - |
Description
The collected data is different between two consequent runs of the backend, so it cannot be used as a valid test.
History
#1
Updated by George Notaras about 3 years ago
- Due date set to 04/09/2010
- Status changed from New to Assigned
- Estimated time set to 0.50
#2
Updated by George Notaras about 3 years ago
- Assignee set to George Notaras
#3
Updated by George Notaras about 3 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 40
#4
Updated by George Notaras about 3 years ago
- Status changed from Resolved to Feedback
- Target version changed from 0.1.4 to 0.2.0
#5
Updated by George Notaras about 3 years ago
- Priority changed from Urgent to High
Problem is some of the sysctl -a output entries, which contain runtime statistical information.
#6
Updated by George Notaras about 3 years ago
- Priority changed from High to Normal
#7
Updated by George Notaras about 3 years ago
- Due date changed from 04/09/2010 to 04/14/2010
- Target version changed from 0.2.0 to 0.1.7
#8
Updated by George Notaras about 3 years ago
- Target version deleted (
0.1.7) - % Done changed from 40 to 50
The sysctl -a command output is not hashed by default. This is resolved for now, but feedback is required.
#9
Updated by George Notaras about 3 years ago
- Priority changed from Normal to Low
#10
Updated by George Notaras about 2 years ago
- Assignee deleted (
George Notaras)
