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.

Sign up for GitHub

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

Jump to bottom

CI failures after clang/valgrind update #968

Closed
2 tasks
real-or-random opened this issue Aug 18, 2021 · 0 comments · Fixed by #969
Closed
2 tasks

CI failures after clang/valgrind update #968

real-or-random opened this issue Aug 18, 2021 · 0 comments · Fixed by #969

Comments

@real-or-random
Copy link
Contributor

real-or-random commented Aug 18, 2021 •
edited
Loading

After the most recent rebuild of our cirrus docker image (no idea what triggered the rebuild but it's just a cached which can be cleared at any time), we know have clang 11 (previously clang 7), valgrind 3.16 (previously 3.14) and also new gcc version.

This causes some CI builds to fail, see for example https://cirrus-ci.com/build/5697283367895040:

  • sanitizers with gcc
  • valgrind with clang

I'll have a look.
@real-or-random real-or-random linked a pull request Aug 19, 2021 that will close this issue
ci: Fixes after Debian release #969
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci: Fixes after Debian release real-or-random/secp256k1
1 participant
@real-or-random