core/internal/common/supervisor: deflake

We fix several flaky tests in the supervisor framework, and one bug in the
supervisor itself.

Tests are deflaked by depending less on tight timing and instead on a
'settled' state of the supervisor, which is basically a wait to join the
supervisor when it's done with whatever work it's currently taking care
of.

Another flake, TestBackoff, is fixed by widening the allowed restart
time.

Finally, we fix a bug in the supervisor that caused it to spuriously
restart children when it would schedule them when their future parents
context was canceled.

Finally, we make some log messages less verbose.

Test Plan: Covered by existing tests that are now less flaky. This was tested with bazel test --runs_per_test=100 to not flake anymore.

X-Origin-Diff: phab/D495
GitOrigin-RevId: f92f7368708c54c59644d3e7dca03b2b5692c30a
5 files changed
tree: 340b921508eba906823c28740b2010733d108c13
  1. build/
  2. core/
  3. scripts/
  4. third_party/
  5. .bazelignore
  6. .bazelrc
  7. BUILD
  8. nogo_config.json
  9. README.md
  10. WORKSPACE
README.md

Nexantic monorepo

This is the monorepo storing all of nexantic's internal projects and libraries.

Environment

We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.

For better reproducibility, all builds are executed in containers.

Usage

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)

IntelliJ

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.