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

Fix build of several projects #11936

Closed
wants to merge 1 commit into from

Conversation

guidovranken
Copy link
Contributor

Spent a lot of time trying to fix build with new clang/AFL (#11714) but didn't succeed right now so disabling AFL for some projects.

Copy link

guidovranken is either the primary contact or is in the CCs list of projects/nettle.
guidovranken has previously contributed to projects/nettle. The previous PR was #11431
guidovranken is either the primary contact or is in the CCs list of projects/cryptofuzz.
guidovranken has previously contributed to projects/cryptofuzz. The previous PR was #11845
guidovranken is either the primary contact or is in the CCs list of projects/circl.
guidovranken has previously contributed to projects/circl. The previous PR was #11431

Copy link
Contributor

@jonathanmetzman jonathanmetzman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jonathanmetzman
Copy link
Contributor

Is it fine to merge this despite the failures?

@guidovranken
Copy link
Contributor Author

Is it fine to merge this despite the failures?

Yes this + #11943 should make the projects succeed.

@guidovranken
Copy link
Contributor Author

Can this be merged? Optionally retrigger CI; now that #11943 has been merged, it should succeed now

@maflcko
Copy link
Contributor

maflcko commented May 14, 2024

You can also rebase or merge with current master, or re-open to re-trigger CI, I think.

@@ -13,7 +13,6 @@ architectures:
main_repo: 'https://git.lysator.liu.se/nettle/nettle'

fuzzing_engines:
- afl
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this needed? The nettle build is now passing, see https://oss-fuzz-build-logs.storage.googleapis.com/index.html#nettle , so afl should not be needed to be removed for that reason.

If you want to do it with the goal of un-pinning the project, I'd say it should be done in the same pull request. That is, also include the following diff:

diff --git a/projects/nettle/Dockerfile b/projects/nettle/Dockerfile
index f667134aa..ef95c688d 100644
--- a/projects/nettle/Dockerfile
+++ b/projects/nettle/Dockerfile
@@ -14,8 +14,7 @@
 #
 ################################################################################
 
-FROM gcr.io/oss-fuzz-base/base-builder@sha256:19782f7fe8092843368894dbc471ce9b30dd6a2813946071a36e8b05f5b1e27e
-# ! Project pinned after a clang update and an afl link error. Log: https://oss-fuzz-gcb-logs.storage.googleapis.com/log-e701b6fa-f3a0-414e-ad6e-0223e6d42ebd.txt
+FROM gcr.io/oss-fuzz-base/base-builder
 RUN apt-get update && apt-get install -y software-properties-common make autoconf build-essential wget lzip libtool python
 RUN git clone --depth 1 https://git.lysator.liu.se/nettle/nettle
 RUN git clone --depth 1 https://github.com/randombit/botan.git

@guidovranken
Copy link
Contributor Author

Overridden by #11959

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

Successfully merging this pull request may close these issues.

4 participants