From b27c53b15f820a3dd8fdab455f3f7f2b1d4ac9c5 Mon Sep 17 00:00:00 2001
From: Alex Crichton <alex@alexcrichton.com>
Date: Sun, 29 Dec 2013 17:34:15 -0800
Subject: [PATCH] Fix a deadlock in a libgreen test

Turns out when you grab an OS mutex, you need to be careful about when and where
things are scheduled!
---
 src/libgreen/sched.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/libgreen/sched.rs b/src/libgreen/sched.rs
index b63c3d92da3ee..984cc88a4c956 100644
--- a/src/libgreen/sched.rs
+++ b/src/libgreen/sched.rs
@@ -1433,7 +1433,7 @@ mod test {
             drop(handle);
 
             let mut handle = pool.spawn_sched();
-            handle.send(TaskFromFriend(pool.task(TaskOpts::new(), proc() {
+            handle.send(PinnedTask(pool.task(TaskOpts::new(), proc() {
                 // Wait until the other task has its lock
                 start_po.recv();