On Sun, Feb 26, 2017 at 8:39 AM, Dave Page <dpage@pgadmin.org> wrote:
>
> On the plus side, test runs are now green across the board with
> feature tests enabled, except for Python 2.6 :-)
I say that, however...
- I've now seen the same error with Python 3.6 as with 2.6, yet whilst
it's consistent on 2.6, it's intermittent on 3.6. I've also seen it on
other versions of Python though, less often than on 3.6 or 2.6.
- One or both of the feature tests seem to be failing ~90% of the time
with 2.7. It seems almost random as to which one will fail, and on
which database server:
Traceback (most recent call last):
File
"/var/lib/jenkins/workspace/pgadmin4-master-python27/web/pgadmin/feature_tests/connect_to_server_feature_test.py",
line 23, in setUp
super(ConnectsToServerFeatureTest, self).setUp()
File "/var/lib/jenkins/workspace/pgadmin4-master-python27/web/regression/feature_utils/base_feature_test.py",
line 19, in setUp
self.page.wait_for_app()
File "/var/lib/jenkins/workspace/pgadmin4-master-python27/web/regression/feature_utils/pgadmin_page.py",
line 110, in wait_for_app
self._wait_for("app to start", page_shows_app)
File "/var/lib/jenkins/workspace/pgadmin4-master-python27/web/regression/feature_utils/pgadmin_page.py",
line 124, in _wait_for
raise AssertionError("timed out waiting for " + waiting_for_message)
AssertionError: timed out waiting for app to start
Unfortunately, I don't see the actual assertion message. It would be
nice to know what waiting_for_message contained.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
