nerves-project / nerves

Craft and deploy bulletproof embedded software in Elixir
http://nerves-project.org
Apache License 2.0
2.23k stars 189 forks source link

nerves.system.shell information out of order #921

Open LostKobrakai opened 10 months ago

LostKobrakai commented 10 months ago

Environment

|nerves_bootstrap| Loadpaths Start

|nerves_bootstrap| Precompile Start

==> nerves_toolchain_x86_64_nerves_linux_musl |nerves_bootstrap| Compile.NervesPackage start

|nerves_bootstrap| Compile.NervesPackage end

==> nerves_system_da_1000 Generated nerves_system_da_1000 app |nerves_bootstrap| Compile.NervesPackage start

|nerves_bootstrap| Compile.NervesPackage end

|nerves_bootstrap| Precompile End

Nerves environment MIX_TARGET: target MIX_ENV: dev

|nerves_bootstrap| Environment Variable List target: target toolchain: /home/benni/.nerves/artifacts/nerves_toolchain_x86_64_nerves_linux_musl-linux_x86_64-1.8.0 system: /home/benni/.nerves/artifacts/nerves_system_da_1000-portable-0.0.1 app: .

|nerves_bootstrap| Loadpaths End

* Additional information about your host, target hardware or environment that
  may help

### Current behavior

Running the command I occationally get the result in incorrect order:

benni@jester:~/nerves-system-da-1000$ mix nerves.system.shell ==> nerves ==> nerves_system_da_1000 |nerves_bootstrap| shell start deprecated /home/benni/nerves-system-da-1000/deps/nerves_system_br/create-build.sh /home/benni/nerves-system-da-1000/nerves_defconfig /home/benni/nerves-system-da-1000/.nerves/artifacts/nerves_system_da_1000-portable-0.0.1 >/dev/null && cd /home/benni/nerves-system-da-1000/.nerves/artifacts/nerves_system_da_1000-portable-0.0.1 OTP 26 made several changes to the serial interface handling. Unfortunately, this is a regression in preventing the Nerves tooling from starting a system sub-shell.

However, compilation is supported on this host and this native shell can be used. Run the commands below to create the build directory and perform all the same interactions as before within it:



### Expected behavior

Proper order of information.
jjcarstens commented 10 months ago

I've investigated this a little bit, but don't have any more leads. The final command is in its own log statement so that it could be shoved to stdin for the hacky workarounds. I thought it my be due to logger being async and out of order, but @LostKobrakai has also discovered some issues with the shell duplicating messages when using SSH and NervesHub