Skip to content

Fix ci build with valgrind (LEVEL=nightmare) #30

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Open
ololobus opened this issue Oct 30, 2020 · 0 comments
Open

Fix ci build with valgrind (LEVEL=nightmare) #30

ololobus opened this issue Oct 30, 2020 · 0 comments

Comments

@ololobus
Copy link
Contributor

Now it throws a weird error:

+ valgrind --tool=memcheck --leak-check=no --time-stamp=yes --track-origins=yes --trace-children=yes --gen-suppressions=all --suppressions=/pg/testdir/postgresql/src/tools/valgrind.supp --suppressions=/pg/testdir/valgrind.supp --log-file=/tmp/valgrind-%p.log pg_ctl start -l /tmp/postgres.log -w
438valgrind: /pg/testdir/pg_bin/bin/pg_ctl: Operation not permitted

For example: https://travis-ci.com/github/postgrespro/pg_variables/jobs/418807062#L438

It could be related to a problem with setrlimit(RLIMIT_CORE, &lim); inside container: https://stackoverflow.com/questions/52070477/setrlimit-fails-with-operation-not-permitted-when-run-under-valgrind
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ololobus