Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B491C200B5B for ; Fri, 5 Aug 2016 12:23:44 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B19BC160A8E; Fri, 5 Aug 2016 10:23:44 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EF3F5160A6D for ; Fri, 5 Aug 2016 12:23:43 +0200 (CEST) Received: (qmail 99220 invoked by uid 500); 5 Aug 2016 10:23:43 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 99209 invoked by uid 99); 5 Aug 2016 10:23:42 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2016 10:23:42 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id C87CBEC22C; Fri, 5 Aug 2016 10:23:42 +0000 (UTC) From: aledsage To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #289: Fix non-deterministic test of SpecParameter by c... Content-Type: text/plain Message-Id: <20160805102342.C87CBEC22C@git1-us-west.apache.org> Date: Fri, 5 Aug 2016 10:23:42 +0000 (UTC) archived-at: Fri, 05 Aug 2016 10:23:44 -0000 Github user aledsage commented on the issue: https://github.com/apache/brooklyn-server/pull/289 LGTM - the previous version of the test is most confusing as to what the expected behaviour was! The new assertions look much more correct. Merging now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---