| Commit-Queue | +1 |
This is an initial, slightly hacky suggestion. Is there a better place to put this?
Would we want this more generically?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I'm actually checking if the d8 change is needed at all. See http://b/490084113#comment8 - need to investigate CF code.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
I'm actually checking if the d8 change is needed at all. See http://b/490084113#comment8 - need to investigate CF code.
Hold off... I think I can just drop the d8 change again.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
directory, assuming that Clusterfuzz runs V8 from the build
directory.| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This is an initial, slightly hacky suggestion. Is there a better place to put this?
Would we want this more generically?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[fuzzing] Add a fallback to load the wasm-module-builder
This makes it possible to run test cases that lack access to the
wasm module builder but reference in their code:
d8.file.execute('test/mjsunit/wasm/wasm-module-builder.js');
For Clusterfuzz archives, the file is bundled in the build
directory, assuming that Clusterfuzz runs V8 from the build
directory.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This breaks the build for me. Now it just removes the js file from my checkout and then the build fails.
$ ninja -C out.gn/x64.release
ninja: Entering directory `out.gn/x64.release'
[0/1] Regenerating ninja files
[1132/5216] COPY ../../test/mjsunit/wasm/wasm-module-builder.js test/mjsunit/wasm/wasm-module-builder.js
FAILED: test/mjsunit/wasm/wasm-module-builder.js
ln -f ../../test/mjsunit/wasm/wasm-module-builder.js test/mjsunit/wasm/wasm-module-builder.js 2>/dev/null || (rm -rf test/mjsunit/wasm/wasm-module-builder.js && cp -af ../../test/mjsunit/wasm/wasm-module-builder.js test/mjsunit/wasm/wasm-module-builder.js)
cp: cannot stat '../../test/mjsunit/wasm/wasm-module-builder.js': No such file or directory
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This breaks the build for me. Now it just removes the js file from my checkout and then the build fails.
$ ninja -C out.gn/x64.release
ninja: Entering directory `out.gn/x64.release'
[0/1] Regenerating ninja files
[1132/5216] COPY ../../test/mjsunit/wasm/wasm-module-builder.js test/mjsunit/wasm/wasm-module-builder.js
FAILED: test/mjsunit/wasm/wasm-module-builder.js
ln -f ../../test/mjsunit/wasm/wasm-module-builder.js test/mjsunit/wasm/wasm-module-builder.js 2>/dev/null || (rm -rf test/mjsunit/wasm/wasm-module-builder.js && cp -af ../../test/mjsunit/wasm/wasm-module-builder.js test/mjsunit/wasm/wasm-module-builder.js)
cp: cannot stat '../../test/mjsunit/wasm/wasm-module-builder.js': No such file or directory
Strange, I don't see that behavior. What GN flags do you use? Is this in connection to this cluster build maybe? In this case, feel free to skip this target behind this GN flag.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |