Skip to content
This repository was archived by the owner on Nov 1, 2023. It is now read-only.

LibFuzzer coverage task failed to synchronize coverage to container #542

Closed
jagunter opened this issue Feb 11, 2021 · 1 comment · Fixed by #588
Closed

LibFuzzer coverage task failed to synchronize coverage to container #542

jagunter opened this issue Feb 11, 2021 · 1 comment · Fixed by #588
Assignees
Labels
bug Something isn't working

Comments

@jagunter
Copy link

Information

  • Onefuzz version: 2.4.1
  • OS: MicrosoftWindowsDesktop:Windows-10:20h2-pro:latest

Provide detailed reproduction steps (if any)

Job was submitted with the following arguments:

onefuzz template libfuzzer basic --setup_dir <setup> --target_exe <target> --inputs <inputs> --duration 72 --notification_config <config> --reboot_after_setup -v <project> <name> <build> <pool>
  1. Submit artifacts of job id 40eee076-df8b-4c4f-b6cd-4970625fde1b from the internal instance.
  2. Wait ~20 minutes
  3. Verify coverage files are not synchronized to container
  4. Connect to host directly via SSH or RDP and confirm coverage files have been generated locally

Expected result

Coverage files would appear in container

Actual result

Coverage files do not appear in container

@jagunter jagunter added the bug Something isn't working label Feb 11, 2021
@ghost ghost added the Needs: triage label Feb 11, 2021
@bmc-msft bmc-msft self-assigned this Feb 16, 2021
@bmc-msft bmc-msft linked a pull request Mar 1, 2021 that will close this issue
@bmc-msft
Copy link
Contributor

bmc-msft commented Mar 1, 2021

@jagunter we fixed an issue that we believe addresses this issue, #542.

@bmc-msft bmc-msft closed this as completed Mar 1, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Mar 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants