| commit | fc2c4f5bc24286f24d3fe130bec61cf9fc59982d | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Wed May 06 19:26:32 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Wed May 06 19:26:32 2020 +0200 |
| tree | f467337f1cc022eb06f0d6655a239af7a4a41723 | |
| parent | ac6b6441f65fa160c1a3d2e9b31277e747c96a32 [diff] |
ci: enable race detector in tests The Go race detector [1] allows to detect runtime data races between Goroutines. Adding it to the test suite can increase runtime significantly (by around 20x), but for the amount of tests we have right now it should be acceptable to always run them on every diff in CI. [1] - https://golang.org/doc/articles/race_detector.html Test Plan: consider the test runtime increase before merging X-Origin-Diff: phab/D496 GitOrigin-RevId: 655a9ae3d3b4d72eae26180434f685193de6d9a7
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.