Bas van Gijzel

Should modify the documentation to not use AllInDar in production code.

Check whether these tests are using sandbox on x, as they will need to be migrated.

Given the discussion I would probably just up the timing for the SBuiltinBigNumericTest.

Gary: ignore M1 tests for now given the completely unrelated flakes Sam: Windows test needs changes to a Shake rule so we can properly propagate. ``` FAIL: //compiler/damlc/tests:daml-doctest (see C:/users/u/_bazel_u/lwsr2dl2/execroot/com_github_digital_asset_daml/bazel-out/x64_windows-opt/testlogs/compiler/damlc/tests/daml-doctest/test.log)...

Rémy: * some flaky triggers? * JSON API flaky on Oracle https://dev.azure.com/digitalasset/daml/_build/results?buildId=147989&view=logs&jobId=52c0dd40-3465-5e8e-2f7c-ae591b3bddfa&j=52c0dd40-3465-5e8e-2f7c-ae591b3bddfa&t=199b63e7-8a1c-52a3-a4d5-f2bcbcf31b17 //ledger-service/http-json:integration-tests-ce_test_suite_src_it_scala_http_WebsocketServiceIntegrationTest.scala

Caused by a difference in MacOS and Linux behaviour.

> multi-package tests: > > ``` > Changing ghc-options, or other `build-options` should invalidate the cache: FAIL > Exception: ./package-b/daml.yaml: openFile: resource busy (file is locked) > ``` Has not...

Warning added in 2.8. Removal in 2.9 and 3.0.

This will be delayed until Daml 3.x with the DAR management rework.

See https://github.com/digital-asset/daml/pull/17610#issuecomment-1790949941. We should handle the error better for dropping/adding non-optional fields.