From 4b52294773340fb4bf64104d616aeb4911d4bcf4 Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Fri, 10 Oct 2014 22:55:48 +0100 Subject: [PATCH] Specifying assertcond rather than assertline is likely to be more robust against code changes. Copied from Perforce Change: 187203 ServerID: perforce.ravenbrook.com --- mps/test/function/72.c | 2 +- mps/test/testsets/passing | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/mps/test/function/72.c b/mps/test/function/72.c index 946844d9492..6a761742cc2 100644 --- a/mps/test/function/72.c +++ b/mps/test/function/72.c @@ -7,7 +7,7 @@ TEST_HEADER OUTPUT_SPEC assert = true assertfile P= trace.c - assertline = 963 + assertcond = ss->rank < RankEXACT END_HEADER */ diff --git a/mps/test/testsets/passing b/mps/test/testsets/passing index aeb6801c43e..73e11d953f0 100644 --- a/mps/test/testsets/passing +++ b/mps/test/testsets/passing @@ -72,7 +72,7 @@ function/67.c function/69.c function/70.c function/71.c -% function/72.c -- testcase seems bogus +function/72.c function/73.c function/74.c function/75.c