mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
8539873d84
document shared memory segment issue After discussion with @SamirTalwar-DA, we agree the CI script to clear memory segments is a bit too dangerous to make it easy to run on developer machines. Still, developers may run into similar issues if they run lots of tests and/or do not reboot their laptop frequently. On developer laptops, we usually spawn one PostgreSQL instance per build/test that needs it (as opposed to CI where we create a single one for the entire build; see `build.sh`), so they can actually build up fairly quickly in some scenarios. As an alternative, I have added a section to the README to cover what to do if that issue happens. CHANGELOG_BEGIN CHANGELOG_END |
||
|---|---|---|
| .. | ||
| cron | ||
| da-ghc-lib | ||
| docker/daml-sdk | ||
| patch_bazel_windows | ||
| build-unix.yml | ||
| build-windows.yml | ||
| check-changelog.sh | ||
| clear-shared-segments-macos.yml | ||
| compatibility_ts_libs.yml | ||
| compatibility-windows.yml | ||
| compatibility.yml | ||
| configure-bazel.sh | ||
| daily_tell_slack.yml | ||
| dev-env-install.sh | ||
| dev-env-push.py | ||
| postgresql.conf | ||
| report-end.yml | ||
| report-start.yml | ||
| slack_user_ids | ||
| tell-slack-failed.yml | ||
| windows-diagnostics.ps1 | ||