| commit | d026b37c2a27d414821f860ccd0effb522be1ce4 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Mon Feb 13 19:38:45 2023 +0100 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Mon Feb 13 21:01:06 2023 +0000 |
| tree | 223512570e3c0857d7f34e3ee588d21163b213b0 | |
| parent | a01b4ee048e27dc05452912d25d6f718fb263c61 [diff] |
m/n/build: fix incorrect device number The device node major number for our console device is wrong. The major number for the console device is 5, not 1 as seen in Documentation/admin-guide/serial-console.rst. I stumbled upon this when looking at this spec as a reference for an issue with an unrelated device. Change-Id: Icbae264d2b4a5dc8770cb1e15e33d56c504a50c5 Reviewed-on: https://review.monogon.dev/c/monogon/+/1126 Reviewed-by: Leopold Schabel <leo@monogon.tech> Tested-by: Jenkins CI
This is the main repository containing the source code for the Monogon Platform.
This is pre-release software - take a look, and check back later!
Our build environment is self-contained and requires only minimal host dependencies:
/dev/kvm (if you want to run tests).Our docs assume that Bazelisk is available as bazel on your PATH.
Refer to SETUP.md for detailed instructions.
Build CLI and node image:
bazel build //metropolis/cli/dbg //:launch -c dbg
Launch an ephemeral test node:
bazel test //:launch -c dbg --test_output=streamed
Run a kubectl command while the test is running:
bazel-bin/metropolis/cli/dbg/dbg_/dbg kubectl describe node
Run full test suite:
bazel test -c dbg //...