analyzing hashmap.rs uncovered a deeper problem; disable validation there for now

src/librustc_mir/interpret/validation.rs

@@ -129,9 +129,6 @@ fn normalize_projections_in<'a, 'gcx, 'tcx, T>(
             let traits::Normalized { value: result, obligations } =
                 traits::normalize(&mut selcx, param_env, cause, value);
 
-            debug!("normalize_projections_in: result={:?} obligations={:?}",
-                    result, obligations);
-
             let mut fulfill_cx = traits::FulfillmentContext::new();
 
             for obligation in obligations {
@@ -149,8 +146,6 @@ fn drain_fulfillment_cx_or_panic<'a, 'gcx, 'tcx, T>(
                                                 -> T::Lifted
             where T: TypeFoldable<'tcx> + ty::Lift<'gcx>
         {
-            debug!("drain_fulfillment_cx_or_panic()");
-
             // In principle, we only need to do this so long as `result`
             // contains unbound type parameters. It could be a slight
             // optimization to stop iterating early.
@@ -207,8 +202,6 @@ fn my_trans_normalize<'a, 'tcx>(&self,
         fn normalize_associated_type<'a, 'tcx, T>(self_: TyCtxt<'a, 'tcx, 'tcx>, value: &T) -> T
             where T: MyTransNormalize<'tcx>
         {
-            debug!("normalize_associated_type(t={:?})", value);
-
             let param_env = ty::ParamEnv::empty(Reveal::All);
 
             if !value.has_projection_types() {

tests/run-pass-fullmir/hashmap.rs

+// FIXME: disable validation until we figure out how to handle <https://github.com/solson/miri/issues/296>.
+// compile-flags: -Zmir-emit-validate=0
 use std::collections::{self, HashMap};
 use std::hash::BuildHasherDefault;