MIME-Version: 1.0
In-Reply-To: 
 <CAKmZXFTv6rOMoktLiw-wWNaNzH6N0Z-3DxJm9+N5b5h6Q6y_8g@mail.gmail.com>
References: 
 <CAKmZXFTmr2DphVBEKR-bGHQVK2MHZHUea0fhxiWGDwWfVHy+Bg@mail.gmail.com>
 <CA+OCxozZVXSNV1wkHn5Ef-hkvukh+s+QXV-6UbRs4YR7EgjWcw@mail.gmail.com>
 <CAKmZXFTv6rOMoktLiw-wWNaNzH6N0Z-3DxJm9+N5b5h6Q6y_8g@mail.gmail.com>
From: Dave Page <dave.page@enterprisedb.com>
Date: Tue, 4 Oct 2016 15:06:57 +0100
Message-ID: 
 <CA+OCxoyNR_mzGEEUqVXSPdvR-KFU91DoSg9hkyVX31SqVLJV3w@mail.gmail.com>
Subject: Re: Database child node: Cast node patch
To: Priyanka Shendge <priyanka.shendge@enterprisedb.com>
Cc: pgadmin-hackers <pgadmin-hackers@postgresql.org>,
	Kanchan Mohitey <kanchan.mohitey@enterprisedb.com>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgadmin-hackers-owner@postgresql.org

Hi

On Tue, Oct 4, 2016 at 9:01 AM, Priyanka Shendge
<priyanka.shendge@enterprisedb.com> wrote:
> I applied this patch on clean machine and executed testsuite only for "cast"
> node, i did not face any issue.
> When i tried to execute testsuite for all nodes, i get same output as you
> mentioned above e-mail. (As few variable name
> have changed later on in test_utils.py file and those are yet to change in
> server and database API cases. So while importing
> those variables its throwing import error.)  Also, me and Navnath have
> verified that this output is not related to setup.py changes.
> (7175929cab984e070d15eb13625ab50459edf9ca)
>
> Could you please try running testsuite only for cast node (python
> regression/runtests.py --pkg browser.server_groups.servers.databases.casts)
> and let me know if there are any issues.

No, I don't see the issue if I only run the cast tests.

I'm not sure how this helps though - I still see the problem if I run
all tests with the patch applied. If I revert the patch, it goes away.
Therefore it's definitely being triggered by the cast patch, if not,
caused by it.

-- 
Dave Page
VP, Chief Architect, Tools & Installers
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake


-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers