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

Small fixes for tests and CI #2722

Merged
merged 8 commits into from
Jul 31, 2023

Conversation

CountBleck
Copy link
Member

@CountBleck CountBleck commented Jul 21, 2023

Changes proposed in this pull request:
⯈ Ensure all tests are run in CI, including those involving experimental features
⯈ Fix the tokenizer test, as useless as it may be
⯈ Ensure the release fixtures and bindings fixtures are checked
⯈ Fix the typings for the writeFile CLI option, since strings are passed in too
⯈ Make VS Code complain less about variables in tests being redeclared in other files

Closes #2723.

  • I've read the contributing guidelines
  • I've added my name and email to the NOTICE file

@CountBleck CountBleck changed the title Small fixes for the compiler tests and CI Small fixes for tests and CI Jul 21, 2023
.github/workflows/test.yml Outdated Show resolved Hide resolved
@CountBleck
Copy link
Member Author

I just changed the functionality of ASC_FEATURES so it only affects whether the relevant tests are instantiated or not. I'll go to sleep for now, but please do let me know if this is a robust solution.

This change makes ASC_FEATURES only affect whether the instantiate step
is executed, and not whether tests are compiled and fixtures checked.
Although the previous commit ensures the fixtures match for all tests
requiring ASC_FEATURES, this commit ensures these tests can be
instantiated. The list of tests to check will (for now) remain a
whitelist, but since the fixtures of *all* tests are checked by CI, the
PR breaking any excluded test can be found via `git blame` or `git log`.
Although the rest of the compiler switched to Pascal case, this small
test didn't. This equally small fix makes the test work again (instead
of spamming "Identifier").
@CountBleck CountBleck force-pushed the fix-tests-a-little branch 6 times, most recently from 75d6e1e to 6a2b5cc Compare July 23, 2023 16:22
@CountBleck
Copy link
Member Author

@dcodeIO @HerrCai0907 This PR should be fully ready as far as I know.

@CountBleck CountBleck marked this pull request as ready for review July 23, 2023 16:23
@CountBleck CountBleck requested a review from MaxGraey July 23, 2023 16:23
This commit changes compiler tests such that WAT fixtures are compared
in release builds as well. Moreover, the JS and (D)TS bindings are now
compared as well, for both debug and release builds. These changes
should ensure changes to Binaryen or bindings generation that affect the
release WAT or JS/TS bindings respectively must update the broken
compiler tests as well.
No longer shall VS Code cry about interface I in class-implements.ts
already being declared in infer-type.ts and static-array.ts! By the
power of forcing ESM detection!
@CountBleck
Copy link
Member Author

Okay, @MaxGraey, what do you think?

@dcodeIO dcodeIO merged commit 9480469 into AssemblyScript:main Jul 31, 2023
12 checks passed
@CountBleck CountBleck deleted the fix-tests-a-little branch July 31, 2023 16:59
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.

4 participants