only one data point ever for int16receiver?
Bug #964890 reported by
Glyph Lefkowitz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Twisted Benchmarks |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
This graph looks broken: http://
| Changed in twisted-benchmarks: | |
| status: | New → Incomplete |
| status: | Incomplete → New |
| importance: | Undecided → Medium |
Revision history for this message
| Jean-Paul Calderone (exarkun) wrote | #1 |
| Changed in twisted-benchmarks: | |
| status: | New → Confirmed |
To post a comment you must log in.
int16receiver is the same benchmark as int16strings. It's not entirely clear why one datapoint got attributed to a differently named benchmark. Certainly we should fix that reporting, and prevent it from recurring.