pk19604014
98d95cd188
Cleanup: since explorer_fuzzer is now a standard cc_fuzz_test, and runs on all files in the corpus, there's no need for fuzzer_util_test to do the same manually
...
Before:
```
//explorer/fuzzing:fuzzer_util_test PASSED in 18.5s
```
After:
```
//explorer/fuzzing:fuzzer_util_test PASSED in 0.3s
```
2022-08-25 09:06:45 -07:00
Josh Soref
066b103881
Spelling ( #1580 )
...
This PR corrects misspellings identified by the [check-spelling action](https://github.com/marketplace/actions/check-spelling ).
The misspellings have been reported at https://github.com/jsoref/carbon-lang/commit/38a1c1640151899fd6da0442a92557f9543b6280#commitcomment-79197316
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/carbon-lang/commit/173c8f9083a68aa61f7cfe94f720f1e5dc7f1ea3
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com >
2022-07-22 16:14:21 -07:00
pk19604014
98f4bb3110
Changed fuzzer_util_test to not process the full fuzzer corpus, but instead just run on a single file, to minimize friction when making fuzzer proto changes ( #1354 )
...
At least one successful parse is still required for the test to pass.
2022-06-30 14:45:36 -04:00
pk19604014
ed93d95fce
Allow unknown fields in fuzzing text proto ( #1296 )
...
This is to help with frequent build breakages cased by proto changes.
Fuzzer corpus can be periodically auto-regenerated.
Crashing samples from the fuzzer are better 'preserved' in the form of fail_xx.carbon tests.
2022-05-25 15:44:06 -07:00
pk19604014
cdc9428984
Changed the type of parameter in FunctionType ctor from generic Expression to TupleLiteral to match the grammar ( #1272 )
2022-05-20 17:36:17 -07:00
Jon Meow
3b8d4a4910
Adjust test to work in more environments. ( #1231 )
...
The current test is really testing too closely to bazel internals.
2022-05-05 17:16:56 -07:00
pk19604014
150057f260
Added GetRunfilesFile() to be able to reliably determine prelude location under various invocation scenarios
...
The logic is using bazel Runfiles API per Jon's suggestion.
One of the scenarios used by the fuzzing framework is to place the binary and its runfiles into a folder, resulting in a directory layout like this:
[temp dir]
fuzzer
fuzzer.runfiles/
Tested:
bazel test -c opt explorer/fuzzing:explorer_fuzzer
bazel build -c opt explorer/fuzzing:explorer_fuzzer + run the binary from various locations
2022-05-02 10:36:21 -04:00
Jon Meow
309ec35f95
Rename executable_semantics to explorer ( #1188 )
...
Change generated with:
```
#!/usr/bin/bash -eux
# Helper script for renaming pending work.
# Run from the repo root.
# Rename executable_semantics in code.
sed -i 's/executable_semantics/explorer/g' \
$(git grep -l 'executable_semantics' . | grep -v proposals)
sed -i 's/executable semantics/explorer/g' \
$(git grep -l 'executable semantics' . | grep -v proposals)
sed -i 's/Executable semantics/Explorer/g' \
$(git grep -l 'Executable semantics' . | grep -v proposals)
sed -i 's/Executable Semantics/Explorer/g' \
$(git grep -l 'Executable Semantics' . | grep -v proposals)
sed -i 's/EXECUTABLE_SEMANTICS/EXPLORER/g' \
$(git grep -l 'EXECUTABLE_SEMANTICS' . | grep -v proposals)
sed -i 's/ExecutableSemantics/Explorer/g' \
$(git grep -l 'ExecutableSemantics' . | grep -v proposals)
sed -i 's/executable-semantics/explorer/g' \
$(git grep -l 'executable-semantics' . | grep -v proposals)
# This is only needed for the initial move.
mv executable_semantics explorer
mv explorer/fuzzing/executable_semantics_fuzzer.cpp explorer/fuzzing/explorer_fuzzer.cpp
```
Verified with `bazel test ...`
2022-04-29 13:20:25 -07:00
pk19604014
Josh Soref
Jon Meow