From d922ca7efda29b23dfb85abe37aee1641c4fbe05 Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Wed, 19 Jul 2023 14:14:10 +0200 Subject: syz-ci: specify per-manager bisection backports It might be the case that the kernels that are being fuzzed on syz-ci require their own backports to build/test older revisions during bisection. Let users specify it in the syz-ci config. --- tools/syz-testbuild/testbuild.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tools/syz-testbuild') diff --git a/tools/syz-testbuild/testbuild.go b/tools/syz-testbuild/testbuild.go index dac89bfcc..daadff3e3 100644 --- a/tools/syz-testbuild/testbuild.go +++ b/tools/syz-testbuild/testbuild.go @@ -125,7 +125,7 @@ func main() { func test(repo vcs.Repo, bisecter vcs.Bisecter, kernelConfig []byte, env instance.Env, com *vcs.Commit) { compiler, compilerType, linker, ccache := "gcc", "gcc", "ld", "" - bisectEnv, err := bisecter.EnvForCommit(compiler, compilerType, *flagBisectBin, com.Hash, kernelConfig) + bisectEnv, err := bisecter.EnvForCommit(compiler, compilerType, *flagBisectBin, com.Hash, kernelConfig, nil) if err != nil { tool.Fail(err) } -- cgit mrf-deployment