-
Notifications
You must be signed in to change notification settings - Fork 129
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
[Bug] unstable pg_upgrade failed #262
Comments
AFATK, add timeout could not resolve this issue, and -t 600 comes from gpstart's param in CBDB CI. If we change it, all components are affected. |
Update: we have Increased CI resources, try to fix it. |
increasing ci resources doesn't help. https://github.com/cloudberrydb/cloudberrydb/actions/runs/6744120555/job/18339332696 |
db internal log can be downloaded at https://github.com/cloudberrydb/cloudberrydb/suites/17879327237/artifacts/1027090491 |
The problem Ray-Eldath mentioned is not the same problem as this. His problem is disscussed in the latter. 2023-11-03 15:06:33.031038 UTC,,,p31860,th-841484160,,,,0,,,seg1,,,,,"LOG","00000","database system is ready",,,,,,,0,,"xlog.c",8477, |
pg_upgrade failed once again https://github.com/cloudberrydb/cloudberrydb/actions/runs/6820307820/job/18549229016?pr=294 |
@smartyhero please try set MAX_CONNECTIONS = 5 or 10 in |
Okay, I'll take care of it |
PR has been created: #308 |
two unstable tests (this one and #301) which both due to occupied port on the vm do not reoccur since the vm image gets rebuilt yesterday. this is kinda strange because the only change during that rebuild was add keep rerunning in #306 to see whether this resurface. ...and it failed in no time :-( https://github.com/cloudberrydb/cloudberrydb/actions/runs/6938950626/job/18875704817?pr=306 |
We have suffered a long time from flaky case: pg_upgrade. However, we didn't find the root cause and most of PR will retry many times due to that. Ignore this for effiency, issue has been created: apache#262 Authored-by: Zhang Mingli avamingli@gmail.com
@jiaqizho have found some useful info: |
We have suffered a long time from flaky case: pg_upgrade. However, we didn't find the root cause and most of PR will retry many times due to that. Ignore this for effiency, issue has been created: #262 Authored-by: Zhang Mingli avamingli@gmail.com
Noting that we have ignored this test case, can we close this issue? @avamingli |
Sure. |
Cloudberry Database version
No response
What happened
We suffer it for a long time
It seems gpstart timeout after switch binary from gpdb5 -> gpdb6
What you think should happen instead
No response
How to reproduce
https://github.com/cloudberrydb/cloudberrydb/actions/runs/6623396719/job/17990808401?pr=260
Operating System
https://github.com/cloudberrydb/cloudberrydb/actions/runs/6623396719/job/17990808401?pr=260
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: