Skip to content

Conversation

@DavidKorczynski
Copy link
Collaborator

Ref: #14457

Copy link
Contributor

@maflcko maflcko left a comment

Choose a reason for hiding this comment

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

thanks!

Let's see how many project need a project-specific flag.

@DavidKorczynski
Copy link
Collaborator Author

/gcbrun trial_build.py all --fuzzing-engines libfuzzer --sanitizers address

@maflcko
Copy link
Contributor

maflcko commented Dec 11, 2025

The CI says:


Step #4 - "Generate Report": ╔══════════════════════════════════════════════════════════════════════════════════════════╗
Step #4 - "Generate Report": ║                                    FINAL BUILD REPORT                                    ║
Step #4 - "Generate Report": ╠══════════════════════════════════════════════════════════════════════════════════════════╣
Step #4 - "Generate Report": ║ No result files found. This typically means that all upstream builds                     ║
Step #4 - "Generate Report": ║ either timed out or failed catastrophically.                                             ║
Step #4 - "Generate Report": ╚══════════════════════════════════════════════════════════════════════════════════════════╝

@hunsche
Copy link
Contributor

hunsche commented Dec 11, 2025

The CI says:


Step #4 - "Generate Report": ╔══════════════════════════════════════════════════════════════════════════════════════════╗
Step #4 - "Generate Report": ║                                    FINAL BUILD REPORT                                    ║
Step #4 - "Generate Report": ╠══════════════════════════════════════════════════════════════════════════════════════════╣
Step #4 - "Generate Report": ║ No result files found. This typically means that all upstream builds                     ║
Step #4 - "Generate Report": ║ either timed out or failed catastrophically.                                             ║
Step #4 - "Generate Report": ╚══════════════════════════════════════════════════════════════════════════════════════════╝

I'm fixing this here https://github.com/google/oss-fuzz/pull/14470/changes

@DavidKorczynski
Copy link
Collaborator Author

This shouldn't be merged just yet. Likely we want to add some changes to a set of projects accompanying this PR. Will do that once we have the restults from the analysis of the projects

@maflcko
Copy link
Contributor

maflcko commented Dec 16, 2025

Should be fine to rebase and re-run now?

@DavidKorczynski
Copy link
Collaborator Author

Should be fine to rebase and re-run now?

yep, I'll start the trial on after landing this one: #14313

@DavidKorczynski
Copy link
Collaborator Author

/gcbrun trial_build.py all --fuzzing-engines libfuzzer --sanitizers address

@maflcko
Copy link
Contributor

maflcko commented Dec 19, 2025

The infra build was passing now, but I can't see the logs, because for me they are either truncated or have a corrupt encoding.

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.

3 participants