Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[esp-v2]: Fix broken builds by changing spawn strategy #3485

Merged
merged 1 commit into from
Mar 9, 2020

Conversation

nareddyt
Copy link
Contributor

@nareddyt nareddyt commented Mar 9, 2020

Example failure

This only occurs on the fuzzers for some reason, not on Travis CI. Error is similar to bazelbuild/bazel#5640.

Change spawn strategy to sandboxed to work around this. Not sure why it was local to begin with (other than a slight performance improvement).

Tested locally to ensure this spawn strategy will work.

python infra/helper.py build_fuzzers --sanitizer address --engine libfuzzer --architecture x86_64 esp-v2

Signed-off-by: Teju Nareddy [email protected]

[Example failure](https://oss-fuzz-build-logs.storage.googleapis.com/log-8eabbac0-bb8f-4f90-a840-f23efe427e0e.txt)

This only occurs on the fuzzers for some reason, not on Travis CI. Error is similar to bazelbuild/bazel#5640.

Change spawn strategy to `sandboxed` to work around this. Not sure why it was `local` to begin with (other than a slight performance improvement).

Tested locally to ensure this spawn strategy will work.

```
python infra/helper.py build_fuzzers --sanitizer address --engine libfuzzer --architecture x86_64 esp-v2
```

Signed-off-by: Teju Nareddy <[email protected]>
@Dor1s
Copy link
Contributor

Dor1s commented Mar 9, 2020

merging since the failure reportedly didn't occur in Travis anyway

@Dor1s Dor1s merged commit f1c65bc into google:master Mar 9, 2020
@nareddyt nareddyt deleted the espv2-fix-spawn branch March 9, 2020 23:50
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.

2 participants