--test-shard A.B is just broken

[killerswan]

It seems to skip a bunch of tests and the last set is empty...

$ cat src/rustx/demo2.rs 
extern crate extra;

use std::io;

#[main]
fn say_hi () {
   io::println("Hello!!");
}

#[test]
fn testA () {
   assert! (2 + 2 == 4);
}

#[test]
fn testB () {
   assert! (2 + 2 == 4);
}

#[test]
fn testC () {
   assert! (2 + 2 == 4);
}

#[test]
fn testD () {
   assert! (2 + 2 == 4);
}

#[test]
fn testE () {
   assert! (2 + 2 == 4);
}

#[test]
fn testF () {
   assert! (2 + 2 == 4);
}

#[test]
fn testG () {
   assert! (2 + 2 == 4);
}

$ 
$ rustc --test src/rustx/demo2.rs 
...
$ ./demo2 --test-shard 1.3

running 2 tests
test testB ... ok
test testE ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured

rustx $ ./demo2 --test-shard 2.3

running 2 tests
test testC ... ok
test testF ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured

rustx $ ./demo2 --test-shard 3.3

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured

[huonw]

Does it start at 0.3?

[killerswan]

Indeed it does! Thanks!

[pnkfelix]

So is this just a documentation issue?

[brson]

I think I'd like to remove this feature. This was implemented as an attempt to improve our cycle time, but we never deployed it to the bots.