Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[YSQL] flaky test: org.yb.pgsql.TestPgRegressPgMisc.testPgRegressPgMisc #16188

Closed
bmatican opened this issue Feb 22, 2023 · 5 comments
Closed
Assignees
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug kind/failing-test Tests and testing infra priority/medium Medium priority issue

Comments

@bmatican
Copy link
Contributor

bmatican commented Feb 22, 2023

@bmatican bmatican added area/ysql Yugabyte SQL (YSQL) kind/failing-test Tests and testing infra priority/high High Priority status/awaiting-triage Issue awaiting triage labels Feb 22, 2023
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue and removed status/awaiting-triage Issue awaiting triage priority/high High Priority labels Feb 22, 2023
jasonyb pushed a commit that referenced this issue May 3, 2023
Summary:
Regress test yb_pg_select, part of java test TestPgRegressPgMisc,
started consistently failing after commit
9c92d1b titled

    [#16926] ysql: make some regress test indexes ASC

It was missed because the test plan missed that test and Detective, the
internal build/test UI, recently changed to hide muted tests by default.

Update the output to make the test pass.  A followup is planned to make
the query closer to what it is intended to test.  The test is still
flaky from an older reason, so leave the issue open.
Jira Issue(s): DB-5620

Test Plan:
Jenkins: test regex: .*TestPgRegressPgMisc#.*

    ./yb_build.sh fastdebug --gcc11 --java-test TestPgRegressPgMisc

Reviewers: mtakahara

Reviewed By: mtakahara

Subscribers: dmitry, yql

Differential Revision: https://phabricator.dev.yugabyte.com/D25039
@bmatican
Copy link
Contributor Author

@jason-yb seems this test is still failing consistently in ASAN. Is that some timing issue, or some legitimate memory issue?

@jasonyb
Copy link
Contributor

jasonyb commented May 12, 2023

@bmatican, it's an ASAN issue stack depth limit exceeded related to #15682.

@m-iancu
Copy link
Contributor

m-iancu commented Jul 18, 2023

I don't see this failing regularly in ASAN anymore so closing.
No failures in last 12 iterations (96 runs across 8 builds):
https://detective-gcp.dev.yugabyte.com/stability/test?analyze_trends=true&class=org.yb.pgsql.TestPgRegressPgMisc&name=testPgRegressPgMisc

@m-iancu m-iancu closed this as completed Jul 18, 2023
@OlegLoginov
Copy link
Contributor

Reopening due to the reproducible test failure:
ybd asan --java-test org.yb.pgsql.TestPgRegressPgMisc#testPgRegressPgMisc
the error is:

-- Check that stack depth detection mechanism works and                         -- Check that stack depth detection mechanism works and
-- max_stack_depth is not set too high                                          -- max_stack_depth is not set too high
create function infinite_recurse() returns int as                               create function infinite_recurse() returns int as
'select infinite_recurse()' language sql;                                       'select infinite_recurse()' language sql;
\set VERBOSITY terse                                                            \set VERBOSITY terse
select infinite_recurse();                                                      select infinite_recurse();
ERROR:  stack depth limit exceeded                                            | server closed the connection unexpectedly
                                                                              >         This probably means the server terminated abnormally
                                                                              >         before or while processing the request.
                                                                              > connection to server was lost

It should be investigated & fixed in another GHI.

@d-uspenskiy
Copy link
Contributor

ASAN failure is fixed in context of c2e13ef

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug kind/failing-test Tests and testing infra priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

6 participants