Skip to content

[v3-0-test] Raise exception if downgrade can't proceed due to no ab_user table (#50343) - #50351

Merged
kaxil merged 1 commit into
v3-0-testfrom
backport-0f0fc02-v3-0-test
May 12, 2025
Merged

kaxil merged 1 commit into
v3-0-testfrom
backport-0f0fc02-v3-0-test

Conversation

@github-actions

@github-actions github-actions Bot commented May 8, 2025

Copy link
Copy Markdown
Contributor
  • Raise exception if downgrade can't proceed due to no ab_user table

We only log the error that the downgrade can't proceed if the ab_user
table is not found, but we should raise an exception instead.
Currently, the CI migrations don't exit on error, which prevents the necessary tests from running.

Also updated the CI migration tests to export DB manager at the shell
because it seems that's not happening, hence why downgrade is running correctly.

  • result can be none so check before accessing row_count

  • dont raise in unittest mode
    (cherry picked from commit 0f0fc02)

Co-authored-by: Ephraim Anierobi splendidzigy24@gmail.com

…user` table (#50343)

* Raise exception if downgrade can't proceed due to no `ab_user` table

We only log the error that the downgrade can't proceed if the `ab_user`
table is not found, but we should raise an exception instead.
Currently, the CI migrations don't exit on error, which prevents the necessary tests from running.

Also updated the CI migration tests to export DB manager at the shell
because it seems that's not happening, hence why downgrade is running correctly.

* result can be none so check before accessing row_count

* dont raise in unittest mode
(cherry picked from commit 0f0fc02)

Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
@kaxil
kaxil force-pushed the backport-0f0fc02-v3-0-test branch from 76a10a2 to 261b72a Compare May 12, 2025 10:22
@kaxil
kaxil merged commit 909d424 into v3-0-test May 12, 2025
@kaxil
kaxil deleted the backport-0f0fc02-v3-0-test branch May 12, 2025 19:32
kaxil pushed a commit that referenced this pull request Jun 3, 2025
…user` table (#50343) (#50351)

* Raise exception if downgrade can't proceed due to no `ab_user` table

We only log the error that the downgrade can't proceed if the `ab_user`
table is not found, but we should raise an exception instead.
Currently, the CI migrations don't exit on error, which prevents the necessary tests from running.

Also updated the CI migration tests to export DB manager at the shell
because it seems that's not happening, hence why downgrade is running correctly.

* result can be none so check before accessing row_count

* dont raise in unittest mode
(cherry picked from commit 0f0fc02)

Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants