Fix expected error message in build test (#771)

Summary:
This change should have happened in #768. However, I didn’t catch it
then because `yarn test --full` passes even before this commit, despite
the expected error being clearly wrong! It turns out that a very sneaky
bug conspires with this one to result in the test passing no matter what
kinds of warnings `yarn backend` may output. This bug is fixed in #772.

Test Plan:
Observe that the error message is now correct by comparing against the
source in `config/RemoveBuildDirectoryPlugin.js`. Then, apply #772 and
note that `yarn test --full` still passes, but does not pass when #772
is applied and this change is reverted.

wchargin-branch: fix-expected-error-message
This commit is contained in:
William Chargin 2018-09-05 10:41:53 -07:00 committed by GitHub
parent 5e0833421a
commit 1816b13525
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -151,7 +151,7 @@ run_build() {
fi &&
run '"${flags}"' 2>err &&
test_must_fail grep -vF \
-e "Removing build directory: " \
-e "Removing contents of build directory: " \
-e "warn: running `yarn backend`" \
-e "warn: if this offends you" \
-e "info: loading repository" \