I think the RPC-COUNTCALLS test suite should be removed from the normal list of smbtorture tests (defined in 'tests' file) and added to a new set of 'investigational' tests, so that RPC-COUNTCALLS is not normally run as part of smbtorture (for buildfarm, regression testing, etc...)
Other test suites test particular functions of a Windows or Samba server. Its clear if they fail or not and that pass or fail has a useful purpose (indicates something is broken or not).
RPC-COUNTCALLS makes a call request for all opnums 0-500 for all rpc interfaces that are registered with Samba, and then reading the error code that the server returns. Its hard to define a meaningful 'pass' or 'failure' condition.
Consequently, its hard to make sure that a Samba or Windows release will pass this suite. And its hard to see how this is useful for normal testing, so its hard to see the value in spending time making sure Windows and Samba pass and especially continue to pass this suite.
It is clear how this suite is useful for investigating a server and its functions. It looks like thats what RPC-COUNTCALLS was originally built for, afterall, many of the pipes it tries to connect to are named from DCOM interfaces(ex: \pipe\IDispatch), so it may also have been a way to investigate DCOM in addition to investigating RPC.
Either way, its a good investigational tool, but I don't think is appropriate for regular testing of Samba or Windows.
Moving it out of the regular set of 'tests' run and into an 'investigational' set, will save developer time.