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

PostgreSQL server terminated abnormally during the test #10107

Closed
y-yagi opened this Issue Sep 12, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@y-yagi

y-yagi commented Sep 12, 2018

Recently, PostgreSQL server abnormally terminated during test execution of rails/rails repository.

https://travis-ci.org/rails/rails/jobs/427502723#L2940-L2942
https://travis-ci.org/rails/rails/jobs/427496382#L2921-L2923
https://travis-ci.org/rails/rails/jobs/427470858#L2921-L2923
https://travis-ci.org/rails/rails/jobs/427451232#L2921-L2923

If such an error occurs, what is considered to be the cause?
Is it possible to see the log of PostgreSQL server?

In addition, we recently changed the setting to use MySQL 5.7 on Travis CI, and this error occurs.
rails/rails@cd8be30

@BanzaiMan

This comment has been minimized.

Show comment
Hide comment
@BanzaiMan

BanzaiMan Sep 12, 2018

Member

Hmm. One obvious possibility is running out of memory, but without the logs it is hard to say. Seeing that your build is running with sudo, adding the following might give you some insight:

after_failure:
  - sudo cat /var/log/postgresql/postgresql-*-main.log
Member

BanzaiMan commented Sep 12, 2018

Hmm. One obvious possibility is running out of memory, but without the logs it is hard to say. Seeing that your build is running with sudo, adding the following might give you some insight:

after_failure:
  - sudo cat /var/log/postgresql/postgresql-*-main.log
@y-yagi

This comment has been minimized.

Show comment
Hide comment
@y-yagi

y-yagi Sep 12, 2018

Thank you for all the details. I will try it.

y-yagi commented Sep 12, 2018

Thank you for all the details. I will try it.

@DrTorte DrTorte added the support label Sep 13, 2018

@y-yagi

This comment has been minimized.

Show comment
Hide comment
@y-yagi

y-yagi Sep 13, 2018

It was because the ramfs was full.
https://travis-ci.org/rails/rails/jobs/427960998#L7614

Since it seems that this problem does not occur if it is container-based infrastructure, I will adjust it to be container-based or extend ramfs to deal with it. Thank you!

y-yagi commented Sep 13, 2018

It was because the ramfs was full.
https://travis-ci.org/rails/rails/jobs/427960998#L7614

Since it seems that this problem does not occur if it is container-based infrastructure, I will adjust it to be container-based or extend ramfs to deal with it. Thank you!

@y-yagi y-yagi closed this Sep 13, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment