From 70857b2ab2b7cbe06b21f8cb896adc12b5be7b03 Mon Sep 17 00:00:00 2001 From: Miha Zupan Date: Fri, 17 May 2024 16:11:33 +0200 Subject: [PATCH] Tweak OneFuzz workaround comment --- eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml b/eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml index 0cc9e4b8212c3..a26558ee148ff 100644 --- a/eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml +++ b/eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml @@ -53,7 +53,9 @@ extends: publish/DotnetFuzzing.exe prepare-onefuzz deployment displayName: Prepare OneFuzz deployment -# Temporary workaround - at the moment OneFuzz can't handle a single deployment where multiple jobs share similar assemblies/pdbs +# OneFuzz can't currently handle a single deployment where multiple jobs share similar assemblies/pdbs. +# As a workaround, we emit a task for every fuzzing target individually. +# https://fuzzfest.visualstudio.com/Onefuzz/_workitems/edit/191504/ is tracking this issue. # - task: onefuzz-task@0 # inputs: # onefuzzOSes: 'Windows'