Unstable test: integration.test_tables.test_tables_pandas

Description

Error:

The first data frame comes back from the backend. The second is from the client test setup. It looks like the client is expecting row ID starting at 0, and row version starting at 0. However, the backend returns both starting at 1. This test doesn’t update the table after creation, so the data must not be out of date.

Environment

Python 3.5+

Activity

Show:
Kimyen Truong
June 22, 2019, 1:32 AM

On prod, I created a table and add a new row (using SWC), then downloaded the data:

On staging:

 

Kimyen Truong
June 22, 2019, 1:37 AM

Adding , and here.

Besides the Python client integration tests, I don’t think anyone is looking at RowID and RowVersion, so it’s a low risk. I’m making notes about this in case someone runs into this problem next week.

Also, the synapser client integration tests passed because it doesn’t check for content coming back.

Kimyen Truong
June 25, 2019, 1:41 AM

, you can use the develop branch to build against new stack for pre-release check. There is no new API changes to the develop branch.

Kimyen Truong
June 28, 2019, 9:22 PM

, I have pushed this fixed to pypi under version 1.9.3. The source code on master branch is also updated. Your build from master branch should no longer fail at this test. The next time you run the build, can you validate this ticket? Thank you.

Xavier Schildwachter
June 28, 2019, 11:09 PM

Verified fixed on dev branch against dev-269.

Assignee

Kimyen Truong

Reporter

Kimyen Truong

Labels

Validator

Xavier Schildwachter

Development Area

None

Release Version History

None

Components

Fix versions

Affects versions

Priority

Major
Configure