ignore various sample tests

2 files changed, 3 insertions, 3 deletions

diff --git a/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md b/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md
index 3801a5b8c7b..d1cd41e0ff6 100644
--- a/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md
+++ b/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization.md
@@ -17,7 +17,7 @@ to that set; moving from a local variable removes it from that set.
 
 Consider this example:
 
-```rust
+```rust,ignore
 fn foo() {
     let a: Vec<u32>;
     
diff --git a/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization/move_paths.md b/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization/move_paths.md
index 7a1239db120..c9e22a81c4c 100644
--- a/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization/move_paths.md
+++ b/src/doc/rustc-dev-guide/src/borrow_check/moves_and_initialization/move_paths.md
@@ -4,7 +4,7 @@ In reality, it's not enough to track initialization at the granularity
 of local variables. Rust also allows us to do moves and initialization
 at the field granularity:
 
-```rust
+```rust,ignore
 fn foo() {
     let a: (Vec<u32>, Vec<u32>) = (vec![22], vec![44]);
     
@@ -41,7 +41,7 @@ the [`move_paths` field of the `MoveData`][move_paths]. For example,
 to convert a [`MovePathIndex`] `mpi` into a MIR [`Place`], you might
 access the [`MovePath::place`] field like so:
 
-```rust
+```rust,ignore
 move_data.move_paths[mpi].place
 ```