mirror of
https://github.com/digital-asset/daml.git
synced 2024-11-10 10:46:11 +03:00
34ae06414e
Previously we ran `daml codegen js` and `daml build` in the tests and we also ran it twice. While this makes sense for the SDK integration tests, it doesn’t really make sense for the compatibility tests. These are SDK-only features so they don’t actually test compatibility. These steps are super slow and running them in the tests also means that we run them a quadratic number of times. This PR moves the `daml build` and the `daml codegen js` step to separate genrules. In the actual test, the only expensive steps are to run `yarn install` and the actual jest tests. In principle, we could probably try to factor out the `yarn install` step as well but I’m a bit scared of coyping around node_modules so I’ll not attempt to do that for now. changelog_begin changelog_end |
||
|---|---|---|
| .. | ||
| client_server | ||
| create-daml-app | ||
| daml_ledger | ||
| daml_script | ||
| test_utils | ||
| BUILD | ||
| create_daml_app_test.sh | ||
| daml_ledger_test.sh | ||
| daml_sdk.bzl | ||
| daml.cc.tpl | ||
| sandbox-with-postgres.sh | ||
| testing.bzl | ||
| versions.bzl | ||