adding libra to list of projects

[mimoo]

Hey!

I'd like to add libra to oss fuzz. Here is the project repository.

Thanks!

[googlebot]

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

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[TravisBuddy]

Hey @mimoo,
Your changes look good to me!

View build log

TravisBuddy Request Identifier: f7ca9f50-4e90-11ea-a3d3-1b6c403325ec

[mimoo]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[inferno-chromium]

Welcome to OSS-Fuzz!

[jonathanmetzman]

Rust fuzzing should 100% work and we are eager to support it.
But there is one sharp edge I know of that I haven't gotten around to investigating, you should probably look at this.
Also, some runtime changes were made by the the first rust project integrated, I'm not sure if those are generally needed: ec58a65 94d0c3a

[mimoo]

thanks for the pointer! I'll report back if I run into troubles :)

[mimoo]

Is there anyway to accept multiple fuzzers as one binary? The way we currently run our fuzzers is that we add a environment variable that specifies which fuzzer it is.

Otherwise I'll have to look into creating separate binaries.

EDIT: made it work on my end

[Dor1s]

OSS-Fuzz model requires multiple binaries. See https://github.com/google/oss-fuzz/pull/431/files for example

[mimoo]

Looks like it takes us more than the 70GB limit to build our fuzzers in release mode 😄 any way to increase this?

[Dor1s]

Are you seeing a failure anywhere, or you've read about 70GB limit in

oss-fuzz/docs/getting-started/new_project_guide.md

Line 261 in d1ed6b8

Our builders have a disk size of 70GB (this includes space taken up by the OS). Builds must keep peak disk usage below this.

?

I see that actual limit is higher, so unless you experience a failure, we should probably fix the docs instead :)

[mimoo]

that's how I had set my docker settings, with more memory it builds!

[Dor1s]

Ack, I've updated the doc in 072457f, sorry for the confusion!

[mimoo]

question: is there a way to invite someone (who hasn't been CC'ed) to a finding?

[Dor1s]

I've granted your gmail account EditIssueCc rights, you should be able to manually CC people on Monorail issues.

[mimoo]

one question: is it possible to grant this to more people/non-google accounts? Also, is there a way on your side to create a distribution list that gets CC'ed? (We can do it on our side, but I'm not sure how it'll work when everybody tries to login as [email protected] on our list.)

[inferno-chromium]

You can add a mailing list in auto_ccs in project.yaml, that sends them email about monorail bug when it is filed, but they wont be able to login to ClusterFuzz interface since that requires individual login.

[mimoo]

what if everyone logs in as [email protected]?

[inferno-chromium]

Then it should work.