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

Get ntp-dev fuzzing again #11589

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Conversation

hart-NTP
Copy link

Update fuzz patch for ntp source changes. (issue 59213).
Speed one-shot build by sharing config.cache between our 4 configure scripts and disabling dependency tracking.
Add Dave Hart and Harlan Stenn to auto_ccs to enable authenticated access to gsutil.

Update fuzz patch for ntp source changes. (issue 59213)
Speed one-shot build by sharing config.cache between our 4 configure scripts and disabling dependency tracking.
Add Dave Hart and Harlan Stenn to auto_ccs to enable authenticated access to gsutil.
Copy link

google-cla bot commented Feb 11, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link

hart-NTP is a new contributor to projects/ntp. The PR must be approved by known contributors before it can be merged. The past contributors are: joycebrum, devtty1er, Dor1s, catenacyber (unverified)

Copy link
Contributor

@catenacyber catenacyber left a comment

Choose a reason for hiding this comment

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

Good for me, thanks for fixing this

Copy link
Contributor

@catenacyber catenacyber left a comment

Choose a reason for hiding this comment

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

Let's run CI

@catenacyber
Copy link
Contributor

@DonggeLiu could you trigger CI please ?

@hart-NTP
Copy link
Author

Thanks, the failing CI runs are due to a bug I've fixed but hasn't been released yet. I will check back after the corrected ntp-dev is released.

[Bug 3835] NTP_HARD_*FLAGS not used by libevent tearoff. hart@ntp.org
https://bugs.ntp.org/3835

@hart-NTP
Copy link
Author

@DonggeLiu could you trigger CI please ?

I've pushed a workaround to hart-NTP/oss-fuzz , would you please, would you please approve the workflow again?

@jonathanmetzman
Copy link
Contributor

Could you fix the errors please?

@hart-NTP hart-NTP force-pushed the davehart-59213 branch 2 times, most recently from 840f3ca to 3cf0b66 Compare May 29, 2024 11:23
@hart-NTP
Copy link
Author

@DonggeLiu please trigger CI again. The corrected ntp-dev was finally released.

Update fuzz patch for ntp source changes. (issue 59213)
Speed one-shot build by sharing config.cache between our 4 configure scripts and disabling dependency tracking.
Add Dave Hart and Harlan Stenn to auto_ccs to enable authenticated access to gsutil.
Adds libevent to Dockerfile prerequisites to build against the current libevent package rather than the copy bundled with the NTP distribution.
Also removes stray newline at end of patch.diff introduced in first attempt
@hart-NTP
Copy link
Author

@catenacyber @DonggeLiu can one of you help approve this to run CI again?

@DavidKorczynski
Copy link
Collaborator

@catenacyber @DonggeLiu can one of you help approve this to run CI again?

done

Revert earlier workaround attempt which attempted avoid broken libevent tearoff now that that tearoff is fixed in ntp-dev.
@hart-NTP
Copy link
Author

Thanks @DavidKorczynski, my earlier attempted workaround for the brokenness in ntp-dev fouled some of the CI runs. I've reverted it and need an approving review to trigger CI again.

@hart-NTP
Copy link
Author

hart-NTP commented Jun 3, 2024

@catenacyber @DavidKorczynski can one of you review to trigger CI please?

@DavidKorczynski
Copy link
Collaborator

@catenacyber @DavidKorczynski can one of you review to trigger CI please?

Done!

@maflcko
Copy link
Contributor

maflcko commented Jun 4, 2024

You can also test the build locally (or in a virtual machine, if you want to keep you local machine clean) with docker python and git installed. See https://google.github.io/oss-fuzz/advanced-topics/reproducing/#building-using-docker

Also, it may be possible to enable GitHub actions in your fork, to run the CI. But I haven't tried that.

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

Successfully merging this pull request may close these issues.

None yet

5 participants