Opened 3 years ago

Last modified 19 months ago

#20504 new defect

When there is only one slice and one scanner, a bwauth runs a second empty slice

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #4269 Points:
Reviewer: Sponsor:

Description

When I run a single bandwidth scanner on less than 50 nodes, configured with:

start_pct = 0
stop_pct = 100
nodes_per_slice = 50

I get the following log message:

NOTICE[Mon Oct 31 04:31:46 2016]:Starting slice for percentiles 100-200
NOTICE[Mon Oct 31 04:31:47 2016]:Only 0 exits remain in slice 100-200 after restrictions. ...
NOTICE[Mon Oct 31 04:31:47 2016]:No routers left after restrictions applied: NodeRestrictionList(['UnmeasuredPercentileRestriction(100,200)', 'OrNodeRestriction(["FlagsRestriction([\'BadExit\'],[])", \'ConserveExitsRestriction()\'])', "FlagsRestriction(['Running'],[])"])

as well as a successful message for the 0-100 slice.

It seems likely that there is an off by one error, either in the handling of start_pct & stop_pct, or in the handling of nodes_per_slice.

Child Tickets

Change History (4)

comment:1 Changed 20 months ago by teor

Parent ID: #4269

comment:2 Changed 20 months ago by teor

Priorities and Severities in torflow are meaningless, setting them all to Medium/Normal.

comment:3 Changed 20 months ago by teor

Owner: aagbsn deleted
Status: newassigned

aagbsn was the default owner, unassigning

comment:4 Changed 19 months ago by teor

Status: assignednew

Mark all tickets that are assigned to nobody as "new".

Note: See TracTickets for help on using tickets.