scripts/run-tests-miri: Disable isolation

fake_i2c's test_no_device_response calls std::thread::sleep, which
fails the test if isolation is enabled.

BUG=None
TEST=./scripts/run-tests-miri

Change-Id: I9cda254ecc0c90909e4f856060aae942dcdbcad9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/hps-firmware/+/3686110
Reviewed-by: Dan Callaghan <dcallagh@chromium.org>
Tested-by: David Lattimore <dml@chromium.org>
Commit-Queue: David Lattimore <dml@chromium.org>
Reviewed-by: Jakub MĹ‚ynarczyk <jakubm@chromium.org>
1 file changed
tree: 0732d6bf450e8798fbad4e8038fa2c875893d601
  1. .vscode/
  2. bin/
  3. buildtools/
  4. docs/
  5. models/
  6. rust/
  7. scripts/
  8. soc/
  9. test_data/
  10. third_party/
  11. toolchain/
  12. .clang-format
  13. .gitignore
  14. .gitmodules
  15. .gn
  16. BUILD.gn
  17. BUILDCONFIG.gn
  18. DIR_METADATA
  19. environment
  20. LICENSE
  21. OWNERS
  22. PRESUBMIT.cfg
  23. pylintrc
  24. README.md
README.md

ChromiumOS HPS

See design document

Initial Setup

  1. Run the setup script. This will set up git submodules and prompt to install missing packages.

    1. ./scripts/setup
  2. To install Radiant you can try to run directly from CLI the extracted binary. In some cases this may fail with “Floating point exception.” error.

    In that case run: `./2.2.0.97.3_Radiant_lin.run --console --prefix ~/lscc/radiant/2.2`
    
    Analogously for any update binaries available.
    
    1. Set RADIANT_DIR to the path where it is installed. e.g. in your .bashrc, you might add:
      1. export RADIANT_DIR=$HOME/lscc/radiant/2.2/bin/lin64
    2. Run sudo ~/lscc/radiant/2.2/programmer/data/vmdata/udevsetup_ubuntu (or one of the other udevsetup scripts) to correctly configure USB subsystem for Radiant.

Building and programming:

Editing code

If your editor has IDE features for Python (e.g. vscode with the Python extension installed), then you should open it with the appropriate environment variables set. e.g.:

(source environment; code .)