Comments only: annotate FIXMEs in tests

src/test/bench/shootout-k-nucleotide.rs

@@ -122,7 +122,7 @@ fn make_sequence_processor(sz: uint, from_parent: comm::port<[u8]>, to_parent: c
 fn main(args: [str]) {
    let rdr = if os::getenv("RUST_BENCH").is_some() {
        // FIXME: Using this compile-time env variable is a crummy way to
-       // get to this massive data set, but #include_bin chokes on it
+       // get to this massive data set, but #include_bin chokes on it (#2598)
        let path = path::connect(
            #env("CFG_SRC_DIR"),
            "src/test/bench/shootout-k-nucleotide.data"

src/test/bench/task-perf-word-count-generic.rs

@@ -77,8 +77,7 @@ mod map_reduce {
 
     type putter<K: send, V: send> = fn(K, V);
 
-    // FIXME: the first K1 parameter should probably be a -, but that
-    // doesn't parse at the moment.
+    // FIXME: the first K1 parameter should probably be a - (#2599)
     type mapper<K1: send, K2: send, V: send> = fn~(K1, putter<K2, V>);
 
     type getter<V: send> = fn() -> option<V>;

src/test/run-pass/basic.rs

@@ -39,7 +39,7 @@ fn main() {
     log(debug, x);
     n = recv(p);
     n = recv(p);
-    // FIXME: use signal-channel for this.
+    // FIXME: use signal-channel for this. (#2600)
     #debug("children finished, root finishing");
 }
 

src/test/run-pass/binops.rs

@@ -60,7 +60,7 @@ fn test_box() {
 }
 
 fn test_port() {
-    // FIXME: Re-enable this once we can compare resources.
+    // FIXME: Re-enable this once we can compare resources. (#2601)
     /*
     let p1 = comm::port::<int>();
     let p2 = comm::port::<int>();

src/test/run-pass/issue-506.rs

@@ -2,6 +2,7 @@
 // FIXME: This test is no longer testing what it was intended to. It should
 // be testing spawning of a native function, but is actually testing
 // spawning some other function, then executing a native function.
+// #2602
 
 /*
   A reduced test case for Issue #506, provided by Rob Arnold.

src/test/run-pass/native-lib-path.rs

@@ -1,4 +1,4 @@
-// xfail-test FIXME I don't know how to test this
+// xfail-test FIXME I don't know how to test this (#2604)
 // compile-flags:-L.
 // The -L flag is also used for linking native libraries
 

src/test/run-pass/task-comm-16.rs

@@ -53,6 +53,7 @@ fn test_tag() {
     send(ch, tag2(10));
     send(ch, tag3(10, 11u8, 'A'));
     // FIXME: Do port semantics really guarantee these happen in order?
+    // (#2605)
     let mut t1: t;
     t1 = recv(po);
     assert (t1 == tag1);

src/test/run-pass/task-compare.rs

@@ -2,7 +2,7 @@
    A test case for issue #577, which also exposes #588
 */
 
-// FIXME: This won't work until we can compare resources
+// FIXME: This won't work until we can compare resources (#2601)
 // xfail-test
 
 use std;