-
Notifications
You must be signed in to change notification settings - Fork 477
Remove usage of legacy build system from build tests #8179
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
Conversation
rescript
@rescript/darwin-arm64
@rescript/darwin-x64
@rescript/linux-arm64
@rescript/linux-x64
@rescript/runtime
@rescript/win32-x64
commit: |
nojaf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm on the fence here.
Tis not really ready to fully rip out rescript-legacy imho.
Won't it be more cathartic if we solve #8178?
It doesn't seem to hard to implement.
|
|
||
| const { execBuildLegacy, execCleanLegacy } = setup(import.meta.dirname); | ||
| // Deactivated because of https://github.com/rescript-lang/rescript/issues/8178 | ||
| process.exit(0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel more inclined to fix #8178 first and not shortcut here.
Yes, that would mean you are not able to remove execBuildLegacy, execCleanLegacy but it would be better to highlight we are not there yet.
| * @param {ExecOptions} [options] | ||
| * @return {Promise<ExecResult>} | ||
| */ | ||
| execBuildLegacy(args = [], options = {}) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See other comment, but I would not remove this just yet.
# Conflicts: # tests/build_tests/duplicated_symlinked_packages/input.js
d34710f to
cc251b2
Compare
|
@nojaf Rebased |
Build Tests: Rewatch Migration
Summary
This change set migrates build tests off the legacy build system and onto the rewatch CLI, updating expectations where output/behavior differs.
Removed
tests/build_tests/in_source(legacy ninja-regenbehavior, followup Rewatch allows two different package specs with the same suffix #8177)tests/build_tests/install(legacy ninja-installbehavior)tests/build_tests/scoped_ppx(legacy ninja command forwarding)tests/build_tests/xpkg(package name_error, followup Rewatch: reserved package names #8176)