| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Images are ready for the commit at 44009eb. To use with deploy scripts, first export MAIN_IMAGE_TAG=4.1.x-541-g44009eb6f0. |
Sorry, something went wrong.
There was a problem hiding this comment.
I think you need some more fixes in the unit tests because of this change:
CommandTag is now an opaque type instead of directly exposing an underlying []byte.
See for example
=== RUN TestAlertDataStore/TestConnExec
conn_test.go:106:
Error Trace: /__w/stackrox/stackrox/pkg/postgres/tests/conn_test.go:106
Error: Expected nil, but got: pgconn.CommandTag{s:""}
Test: TestAlertDataStore/TestConnExec
conn_test.go:112:
Error Trace: /__w/stackrox/stackrox/pkg/postgres/tests/conn_test.go:112
Error: Expected nil, but got: pgconn.CommandTag{s:""}
Test: TestAlertDataStore/TestConnExec
Sorry, something went wrong.
|
Indeed the handling or arrays also changed causing problems https://github.com/jackc/pgx/blob/v5.4.2/CHANGELOG.md?plain=1 |
Sorry, something went wrong.
|
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
Sorry, something went wrong.
|
I haven't had a chance to look at this in detail yet, but I do have a question. What level of testing have we done on this? Reason I ask is that this looks like a significant upgrade and we've seen some things in the past where pgx took some liberties with how they do things. My concern is they adjusted some behaviors and we won't necessarily see them with just vanilla CI. Things we found during scale and chaos type testing would be missed in CI. Additionally should we go through the v5 changelog and write tickets to step up to some of their improved flows such as the new way batching works, etc? |
Sorry, something went wrong.
Agreed, my review was mostly just looking at the changes surface level, but I don't believe we should bump this just because the unit tests pass. I don't know how these upgrades have been done in the past, but I'd be more comfortable with some larger scale tests on the new version. |
Sorry, something went wrong.
|
I concur we need some better test plan. So far I only manually verified some generated queries and besides of map nil serialization I haven't seen any differences. But queries are just a small part of what pgx does. I can enable run UI tests as they run more gql queries. Unfortunately there is no upgrade guide for pgx. I was under the impression it's mostly backward compatible. E.g.: gorm just merged it and released as bugfix release and we already are using this version. Maybe better time to merge it will be just after the release so we will have more time to catch possible bugs. We will need to bump it at some point. |
Sorry, something went wrong.
|
@connorgorman @mtodor could you help with perf/scale tests? |
Sorry, something went wrong.
|
/retest |
Sorry, something went wrong.
|
/test all |
Sorry, something went wrong.
|
/test all |
Sorry, something went wrong.
|
/test all |
Sorry, something went wrong.
|
/retest |
Sorry, something went wrong.
|
@janisz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Sorry, something went wrong.
|
Closing, we can reopen it once we have a proper test plan for this upgrade. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
Important changes in v5:
Checklist
If any of these don't apply, please comment below.
Testing Performed
CI