Re: [pgadmin-hackers] Feature test regression failures
От | Ashesh Vashi |
---|---|
Тема | Re: [pgadmin-hackers] Feature test regression failures |
Дата | |
Msg-id | CAG7mmoxhS-ugNWxtL0YZyUg=G5nXGkf2wApSJinHKhbYxxCHeg@mail.gmail.com обсуждение исходный текст |
Ответ на | [pgadmin-hackers] Feature test regression failures (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: [pgadmin-hackers] Feature test regression failures
|
Список | pgadmin-hackers |
On Thu, Mar 16, 2017 at 3:55 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi Ashesh,
A common theme is emerging from some of the feature test regression
failures on the Jenkins server. Please see:
https://jenkins.pgadmin.org/job/pgadmin4-master-python27/ ws/web/regression/screenshots/ EDB_Postgres_AS_9.3/ ConnectsToServerFeatureTest- 2017.03.16_10.09.18-Python-2. 7.13.png
I've very occasionally seen similar behaviour to this in the past - in
fact it's part of the reason why we grey out the UI until pgAdmin is
fully loaded.
Any idea what might be causing it?
This can happen, when the module is not yet loaded for the respective node, and it is being expanded.
Just thinking - shall we load all the javascript in the beginning?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: