Return-Path: X-Original-To: apmail-incubator-bloodhound-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB605E5F1 for ; Thu, 24 Jan 2013 04:57:21 +0000 (UTC) Received: (qmail 76654 invoked by uid 500); 24 Jan 2013 04:57:21 -0000 Delivered-To: apmail-incubator-bloodhound-commits-archive@incubator.apache.org Received: (qmail 76596 invoked by uid 500); 24 Jan 2013 04:57:21 -0000 Mailing-List: contact bloodhound-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-commits@incubator.apache.org Received: (qmail 76585 invoked by uid 99); 24 Jan 2013 04:57:21 -0000 Received: from bloodhound-vm.apache.org (HELO bloodhound-vm) (140.211.11.32) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2013 04:57:21 +0000 Received: from bloodhound-vm.apache.org (localhost [127.0.0.1]) by bloodhound-vm (Postfix) with ESMTP id D1FE7812CD; Thu, 24 Jan 2013 04:57:20 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Apache Bloodhound" X-Trac-Version: 1.0 Cc: bloodhound-commits@incubator.apache.org Auto-Submitted: auto-generated X-Mailer: Trac 1.0, by Edgewall Software X-Trac-Project: Apache Bloodhound Date: Thu, 24 Jan 2013 04:57:19 -0000 Reply-To: bloodhound-dev@incubator.apache.org X-URL: https://issues.apache.org/bloodhound/ Subject: Re: [Apache Bloodhound] #355: Run Trac test suite against product environments - after #115 #288 X-Trac-Ticket-URL: https://issues.apache.org/bloodhound/ticket/355#comment:11 Message-ID: <070.f6aa108fc70f11fc7da424407f0012b9@incubator.apache.org> References: <055.f95383b8b60cd0fe9638b5798e9b53e7@incubator.apache.org> X-Trac-Ticket-ID: 355 In-Reply-To: <055.f95383b8b60cd0fe9638b5798e9b53e7@incubator.apache.org> #355: Run Trac test suite against product environments - after #115 #288 ---------------------------+------------------------------------ Reporter: olemis | Owner: olemis Type: task | Status: accepted Priority: major | Milestone: Component: multiproduct | Version: Resolution: | Keywords: environment testing QA ---------------------------+------------------------------------ Comment (by olemis): Replying to [comment:10 olemis]: > Replying to [comment:7 jure]: > > Replying to [comment:5 olemis]: > [...] > > > r1437357 solves that, but now tests are failing with the following assertion: > > > [...] > > ~~ It seems to me that this is related to the issue mentioned in comment:8:ticket:288 , but I'm not 100% sure ... yet ... ~~ > > No it's not ... :-$ In the end this was happening because up to this point workflow definition for product environments was empty . [attachment:t115_r1437383_inherit_product_config.diff:ticket:115 A new patch for #115] adds this functionality , thereby after applying patches against r1437383 in this order {{{ #!sh $ hg qapplied t115/t115_r1437383_inherit_product_config.diff t115/t115_r1436300_option_accessor.diff t355/t355_r1437383_trac_test_perm.diff t355/t355_r1437383_trac_test_ticket_api.diff }}} ... ticket API test report looks like this . {{{ #!sh $ python setup.py test -m tests.ticket.api running test running egg_info writing BloodhoundMultiProduct.egg-info/PKG-INFO writing top-level names to BloodhoundMultiProduct.egg-info/top_level.txt writing dependency_links to BloodhoundMultiProduct.egg- info/dependency_links.txt writing entry points to BloodhoundMultiProduct.egg-info/entry_points.txt writing BloodhoundMultiProduct.egg-info/PKG-INFO writing top-level names to BloodhoundMultiProduct.egg-info/top_level.txt writing dependency_links to BloodhoundMultiProduct.egg- info/dependency_links.txt writing entry points to BloodhoundMultiProduct.egg-info/entry_points.txt reading manifest file 'BloodhoundMultiProduct.egg-info/SOURCES.txt' writing manifest file 'BloodhoundMultiProduct.egg-info/SOURCES.txt' running build_ext test_available_actions_chgprop_only (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_available_actions_create_only (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_available_actions_full_perms (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_available_actions_no_perms (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_custom_field_optional_select (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_custom_field_order (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_custom_field_select (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_custom_field_text (tests.ticket.api.ProductTicketSystemTestCase) ... ok test_custom_field_textarea (tests.ticket.api.ProductTicketSystemTestCase) ... ok ---------------------------------------------------------------------- Ran 9 tests in 0.758s OK }}} So I guess that after fixing the issue identified in comment:8:ticket:288 they should all be ready to be applied in `bep_0003_multiproduct` branch . -- Ticket URL: Apache Bloodhound The Apache Bloodhound (incubating) issue tracker