Do not hardcode fuzzers

Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
This commit is contained in:
Kazuyoshi Kato
2022-06-21 16:48:45 +00:00
parent 2b60770c4b
commit f7de1c8f90
2 changed files with 10 additions and 11 deletions

View File

@@ -407,7 +407,7 @@ func doFuzz(data []byte, shouldTearDown bool) int {
// This fuzzer is experimental for now and is being run
// continuously by OSS-fuzz to collect feedback on
// its sustainability.
func FuzzNoTearDownWithDownload(data []byte) int {
func FuzzIntegNoTearDownWithDownload(data []byte) int {
if !haveInitialized {
shouldRestart := initInSteps()
if shouldRestart {
@@ -423,7 +423,7 @@ func FuzzNoTearDownWithDownload(data []byte) int {
// with one minor distinction: One tears down the
// daemon after each iteration whereas the other doesn't.
// The two fuzzers' performance will be compared over time.
func FuzzCreateContainerNoTearDown(data []byte) int {
func FuzzIntegCreateContainerNoTearDown(data []byte) int {
if !haveInitialized {
err := updatePathEnv()
if err != nil {
@@ -438,7 +438,7 @@ func FuzzCreateContainerNoTearDown(data []byte) int {
// FuzzCreateContainerNoTearDown() except that
// FuzzCreateContainerWithTearDown tears down the daemon
// after each iteration.
func FuzzCreateContainerWithTearDown(data []byte) int {
func FuzzIntegCreateContainerWithTearDown(data []byte) int {
if !haveInitialized {
err := updatePathEnv()
if err != nil {