gpio: add per-port input and output level functions

on-target CI success
This is an automated message.

Click to expand...
Output from: git clone git@github.com:newAM/stm32wl-hal.git /tmp/tmpt34obq9z
Cloning into '/tmp/tmpt34obq9z'...

Output from: git checkout b295334d301bb8c58152915670af2d181f5052cb
HEAD is now at b295334 gpio: add per-port input and output level functions

Output from: cargo test -p uart-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling autocfg v1.0.1
   Compiling proc-macro2 v1.0.29
   Compiling unicode-xid v0.2.2
   Compiling semver-parser v0.7.0
   Compiling syn v1.0.76
   Compiling typenum v1.14.0
   Compiling cortex-m v0.7.3
   Compiling semver v1.0.4
   Compiling nb v1.0.0
   Compiling version_check v0.9.3
   Compiling vcell v0.1.3
   Compiling cortex-m-rt v0.6.15
   Compiling void v1.0.2
   Compiling bitfield v0.13.2
   Compiling defmt-parser v0.2.2
   Compiling r0 v0.2.2
   Compiling stable_deref_trait v1.2.0
   Compiling cortex-m v0.6.7
   Compiling stm32wl v0.13.0 (https://github.com/newAM/stm32wl-rs.git?rev=a1aa8eaf9a3d771ccc1752ffff0fa69bf063f009#a1aa8eaf)
   Compiling panic-probe v0.2.0
   Compiling bare-metal v1.0.0
   Compiling paste v1.0.5
   Compiling cfg-if v1.0.0
   Compiling rand_core v0.6.3
   Compiling volatile-register v0.2.1
   Compiling nb v0.1.3
   Compiling semver v0.9.0
   Compiling generic-array v0.14.4
   Compiling num-traits v0.2.14
   Compiling num-integer v0.1.44
   Compiling num-iter v0.1.42
   Compiling num-rational v0.3.2
   Compiling embedded-hal v0.2.6
   Compiling rustc_version v0.2.3
   Compiling bare-metal v0.2.5
   Compiling defmt v0.2.3
   Compiling quote v1.0.9
   Compiling generic-array v0.13.3
   Compiling generic-array v0.12.4
   Compiling num-complex v0.3.1
   Compiling as-slice v0.1.5
   Compiling chrono v0.4.19
   Compiling aligned v0.3.5
   Compiling num v0.3.1
   Compiling embedded-time v0.12.0
   Compiling cortex-m-rt-macros v0.6.15
   Compiling defmt-macros v0.2.3
   Compiling defmt-test-macros v0.2.1
   Compiling defmt-test v0.2.3
   Compiling defmt-rtt v0.2.0
   Compiling stm32wl-hal v0.1.0-alpha.0 (/tmp/tmpt34obq9z/hal)
   Compiling uart-testsuite v0.1.0 (/tmp/tmpt34obq9z/uart-testsuite)
    Finished test [optimized + debuginfo] target(s) in 24.84s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-6a2f77b8d302b33b)
(HOST) INFO  flashing program (13.43 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 WARN  UART tests require C1 (LPUART TX) connected to A10 (UART1 RX) and C0 (LPUART RX) connected to A9 (UART1 TX)
└─ test::tests::init @ tests/test.rs:46
 INFO  (1/3) running `single_byte_loopback_no_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:16
 INFO  (2/3) running `single_byte_loopback_with_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:16
 INFO  (3/3) running `core_fmt`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:16
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:16
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p dac-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling dac-testsuite v0.1.0 (/tmp/tmpt34obq9z/dac-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.35s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-58fba609f98de559)
(HOST) INFO  flashing program (12.70 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/2) running `pin_output`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:15
 INFO  (2/2) running `loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:15
 INFO  DAC out: 1024
└─ test::tests::loopback @ tests/test.rs:75
 INFO  ADC in: 1024
└─ test::tests::loopback @ tests/test.rs:76
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:15
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p pka-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling pka-testsuite v0.1.0 (/tmp/tmpt34obq9z/pka-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.47s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-0ed53d16ac96f8de)
(HOST) INFO  flashing program (17.20 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000008 INFO  (1/10) running `ecdsa_sign`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
0.108633 INFO  (2/10) running `ecdsa_sign_nb`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
0.217258 INFO  (3/10) running `ecdsa_sign_ram_error`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
0.436387 INFO  (4/10) running `ecdsa_sign_mode_error`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
0.655516 INFO  (5/10) running `ecdsa_verify`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
0.874645 INFO  (6/10) running `ecdsa_verify_nb`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
1.093774 INFO  (7/10) running `ecdsa_verify_ram_err`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
1.202398 INFO  (8/10) running `ecdsa_verify_mode_err`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
1.311020 INFO  (9/10) running `ecdsa_verify_invalid_err`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
1.527158 INFO  (10/10) running `ecdsa_doc_keypair`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
1.845842 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:60
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p spi-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling either v1.6.1
   Compiling itertools v0.10.1
   Compiling spi-testsuite v0.1.0 (/tmp/tmpt34obq9z/spi-testsuite)
    Finished test [optimized + debuginfo] target(s) in 1.62s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-1c11d8c7d4a850fc)
(HOST) INFO  flashing program (21.25 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000011 WARN  SPI tests require (SCK, MISO, MOSI) pins SPI1 (A5, A6, A7) connected to SPI2 (A9, C2, C3)
└─ test::tests::init @ tests/test.rs:90
0.000024 INFO  (1/6) running `full_duplex_loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.000049 DEBUG ÷256 MODE_0
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.002288 DEBUG ÷256 MODE_1
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.004696 DEBUG ÷256 MODE_2
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.006954 DEBUG ÷256 MODE_3
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.009362 DEBUG ÷128 MODE_0
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.010655 DEBUG ÷128 MODE_1
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.012038 DEBUG ÷128 MODE_2
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.013330 DEBUG ÷128 MODE_3
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.014713 DEBUG ÷64 MODE_0
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.015527 DEBUG ÷64 MODE_1
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.016382 DEBUG ÷64 MODE_2
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.017196 DEBUG ÷64 MODE_3
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.018051 DEBUG ÷32 MODE_0
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.018638 DEBUG ÷32 MODE_1
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.019226 DEBUG ÷32 MODE_2
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.019813 DEBUG ÷32 MODE_3
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.020402 DEBUG ÷16 MODE_0
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.020876 DEBUG ÷16 MODE_1
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.021351 DEBUG ÷16 MODE_2
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.021825 DEBUG ÷16 MODE_3
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.022301 DEBUG ÷8 MODE_0
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.022720 DEBUG ÷8 MODE_1
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.023140 DEBUG ÷8 MODE_2
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.023559 DEBUG ÷8 MODE_3
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.023979 DEBUG ÷4 MODE_0
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.024349 DEBUG ÷4 MODE_1
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.024719 DEBUG ÷4 MODE_2
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.025089 DEBUG ÷4 MODE_3
└─ test::tests::full_duplex_loopback @ tests/test.rs:98
0.025459 INFO  (2/6) running `full_duplex_loopback_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.025483 DEBUG ÷256 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.027728 DEBUG ÷256 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.030017 DEBUG ÷256 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.032262 DEBUG ÷256 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.034551 DEBUG ÷128 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.035788 DEBUG ÷128 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.037049 DEBUG ÷128 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.038287 DEBUG ÷128 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.039548 DEBUG ÷64 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.040289 DEBUG ÷64 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.041041 DEBUG ÷64 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.041782 DEBUG ÷64 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.042534 DEBUG ÷32 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.043028 DEBUG ÷32 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.043520 DEBUG ÷32 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.044013 DEBUG ÷32 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.044505 DEBUG ÷16 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.044881 DEBUG ÷16 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.045254 DEBUG ÷16 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.045629 DEBUG ÷16 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046002 DEBUG ÷8 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046305 DEBUG ÷8 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046608 DEBUG ÷8 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.046911 DEBUG ÷8 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.047215 DEBUG ÷4 MODE_0
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.047493 DEBUG ÷4 MODE_1
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.047770 DEBUG ÷4 MODE_2
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.048049 DEBUG ÷4 MODE_3
└─ test::tests::full_duplex_loopback_dma @ tests/test.rs:143
0.048326 INFO  (3/6) running `mosi_simplex_loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.048350 DEBUG ÷256 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.049426 DEBUG ÷256 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.050527 DEBUG ÷256 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.051604 DEBUG ÷256 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.052705 DEBUG ÷128 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.053285 DEBUG ÷128 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.053874 DEBUG ÷128 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.054454 DEBUG ÷128 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055043 DEBUG ÷64 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055371 DEBUG ÷64 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.055707 DEBUG ÷64 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056035 DEBUG ÷64 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056371 DEBUG ÷32 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056573 DEBUG ÷32 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056776 DEBUG ÷32 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.056978 DEBUG ÷32 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057181 DEBUG ÷16 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057321 DEBUG ÷16 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057461 DEBUG ÷16 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057601 DEBUG ÷16 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057741 DEBUG ÷8 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057851 DEBUG ÷8 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.057960 DEBUG ÷8 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058070 DEBUG ÷8 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058180 DEBUG ÷4 MODE_0
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058290 DEBUG ÷4 MODE_1
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058399 DEBUG ÷4 MODE_2
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058509 DEBUG ÷4 MODE_3
└─ test::tests::mosi_simplex_loopback @ tests/test.rs:190
0.058618 INFO  (4/6) running `mosi_simplex_loopback_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.058642 DEBUG ÷256 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.059724 DEBUG ÷256 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.060828 DEBUG ÷256 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.061910 DEBUG ÷256 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.063014 DEBUG ÷128 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.063603 DEBUG ÷128 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.064192 DEBUG ÷128 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.064781 DEBUG ÷128 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.065370 DEBUG ÷64 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.065709 DEBUG ÷64 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066045 DEBUG ÷64 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066384 DEBUG ÷64 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066721 DEBUG ÷32 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.066926 DEBUG ÷32 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067132 DEBUG ÷32 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067337 DEBUG ÷32 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067543 DEBUG ÷16 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067683 DEBUG ÷16 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067831 DEBUG ÷16 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.067970 DEBUG ÷16 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068118 DEBUG ÷8 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068230 DEBUG ÷8 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068342 DEBUG ÷8 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068453 DEBUG ÷8 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068565 DEBUG ÷4 MODE_0
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068671 DEBUG ÷4 MODE_1
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068776 DEBUG ÷4 MODE_2
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068882 DEBUG ÷4 MODE_3
└─ test::tests::mosi_simplex_loopback_dma @ tests/test.rs:213
0.068988 INFO  (5/6) running `miso_simplex_loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.069012 DEBUG ÷256 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.070136 DEBUG ÷256 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.071333 DEBUG ÷256 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.072457 DEBUG ÷256 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.073654 DEBUG ÷128 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.074297 DEBUG ÷128 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.074980 DEBUG ÷128 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.075622 DEBUG ÷128 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.076306 DEBUG ÷64 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.076710 DEBUG ÷64 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077134 DEBUG ÷64 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077538 DEBUG ÷64 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.077963 DEBUG ÷32 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078250 DEBUG ÷32 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078542 DEBUG ÷32 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.078829 DEBUG ÷32 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079120 DEBUG ÷16 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079350 DEBUG ÷16 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079580 DEBUG ÷16 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.079810 DEBUG ÷16 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080039 DEBUG ÷8 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080243 DEBUG ÷8 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080446 DEBUG ÷8 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080649 DEBUG ÷8 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.080853 DEBUG ÷4 MODE_0
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081032 DEBUG ÷4 MODE_1
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081211 DEBUG ÷4 MODE_2
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081390 DEBUG ÷4 MODE_3
└─ test::tests::miso_simplex_loopback @ tests/test.rs:247
0.081569 INFO  (6/6) running `miso_simplex_loopback_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
0.081593 DEBUG ÷256 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.082702 DEBUG ÷256 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.083884 DEBUG ÷256 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.084993 DEBUG ÷256 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.086175 DEBUG ÷128 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.086802 DEBUG ÷128 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.087471 DEBUG ÷128 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.088098 DEBUG ÷128 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.088766 DEBUG ÷64 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089153 DEBUG ÷64 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089563 DEBUG ÷64 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.089951 DEBUG ÷64 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090361 DEBUG ÷32 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090632 DEBUG ÷32 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.090909 DEBUG ÷32 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091180 DEBUG ÷32 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091458 DEBUG ÷16 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091672 DEBUG ÷16 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.091886 DEBUG ÷16 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092099 DEBUG ÷16 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092313 DEBUG ÷8 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092501 DEBUG ÷8 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092688 DEBUG ÷8 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.092875 DEBUG ÷8 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093063 DEBUG ÷4 MODE_0
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093226 DEBUG ÷4 MODE_1
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.093390 DEBUG ÷4 MODE_2
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.132653 DEBUG ÷4 MODE_3
└─ test::tests::miso_simplex_loopback_dma @ tests/test.rs:275
0.132817 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:75
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p i2c-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling i2c-testsuite v0.1.0 (/tmp/tmpt34obq9z/i2c-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.48s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-4a58f6b85b8c68fd)
(HOST) INFO  flashing program (21.38 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/2) running `sht31_measurement`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:22
 WARN  A SHT31 sensor must be connected to the board on pins B8 (SCL) & B7 (SDA) for this test to work
└─ test::tests::sht31_measurement @ tests/test.rs:81
 ERROR I2C error: Nack
└─ test::tests::sht31_measurement @ tests/test.rs:88
 INFO  (2/2) running `loopback`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:22
 WARN  I2C1 pins B8 (SCL) and B7 (SDA) must be connected to I2C pins A12 (SCL) and A11 (SDA) for this test to pass
└─ test::tests::loopback @ tests/test.rs:94
 DEBUG I2C2 ISR=0xEE8009
└─ test::__cortex_m_rt_I2C2_EV @ tests/test.rs:114
 DEBUG I2C2 ISR=0xEF800C
└─ test::__cortex_m_rt_I2C2_EV @ tests/test.rs:114
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:22
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p lptim-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling lptim-testsuite v0.1.0 (/tmp/tmpt34obq9z/lptim-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.43s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-7e3059787ba94315)
(HOST) INFO  flashing program (12.37 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000009 INFO  (1/2) running `oneshot`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:25
0.000105 DEBUG 1317404 < 1317504 < 1317604
└─ test::tests::oneshot @ tests/test.rs:96
0.000141 INFO  (2/2) running `oneshot_external_trigger`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:25
0.000164 WARN  Pin B7 must be connected to A11 for this test to pass
└─ test::tests::oneshot_external_trigger @ tests/test.rs:102
0.000237 DEBUG 7466 < 7566 < 7666
└─ test::tests::oneshot_external_trigger @ tests/test.rs:137
0.000273 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:25
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p aes-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling hex-literal v0.3.3
   Compiling aes-testsuite v0.1.0 (/tmp/tmpt34obq9z/aes-testsuite)
    Finished test [optimized + debuginfo] target(s) in 1.32s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-63f23314b915b7e6)
(HOST) INFO  flashing program (52.46 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/14) running `encrypt_ecb_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.000283 INFO  Approximate cycles per 128-bit encrypt: 213
└─ test::tests::encrypt_ecb_128 @ tests/test.rs:1529
0.000305 INFO  (2/14) running `encrypt_ecb_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.000540 INFO  Approximate cycles per 256-bit encrypt: 262
└─ test::tests::encrypt_ecb_256 @ tests/test.rs:1554
0.000562 INFO  (3/14) running `encrypt_ecb_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.000837 INFO  Approximate cycles per 128-bit encrypt: 215
└─ test::tests::encrypt_ecb_inplace_128 @ tests/test.rs:1580
0.000859 INFO  (4/14) running `encrypt_ecb_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.001091 INFO  Approximate cycles per 256-bit encrypt: 259
└─ test::tests::encrypt_ecb_inplace_256 @ tests/test.rs:1604
0.001113 INFO  (5/14) running `encrypt_gcm_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.002523 INFO  Approximate cycles per 128-bit encrypt: 681
└─ test::tests::encrypt_gcm_inplace_128 @ tests/test.rs:1637
0.002545 INFO  (6/14) running `encrypt_gcm_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.004065 INFO  Approximate cycles per 256-bit encrypt: 770
└─ test::tests::encrypt_gcm_inplace_256 @ tests/test.rs:1670
0.004086 INFO  (7/14) running `decrypt_ecb_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.004394 INFO  Average cycles per 128-bit decrypt: 274
└─ test::tests::decrypt_ecb_128 @ tests/test.rs:1695
0.004415 INFO  (8/14) running `decrypt_ecb_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.004718 INFO  Average cycles per 128-bit decrypt: 259
└─ test::tests::decrypt_ecb_inplace_128 @ tests/test.rs:1719
0.004739 INFO  (9/14) running `decrypt_ecb_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.005004 INFO  Average cycles per 256-bit decrypt: 338
└─ test::tests::decrypt_ecb_256 @ tests/test.rs:1744
0.005026 INFO  (10/14) running `decrypt_ecb_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.005289 INFO  Average cycles per 256-bit decrypt: 323
└─ test::tests::decrypt_ecb_inplace_256 @ tests/test.rs:1768
0.005311 INFO  (11/14) running `decrypt_gcm_inplace_128`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.006760 INFO  Approximate cycles per 128-bit decrypt: 698
└─ test::tests::decrypt_gcm_inplace_128 @ tests/test.rs:1801
0.006782 INFO  (12/14) running `decrypt_gcm_inplace_256`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.008305 INFO  Approximate cycles per 256-bit decrypt: 765
└─ test::tests::decrypt_gcm_inplace_256 @ tests/test.rs:1834
0.008327 INFO  (13/14) running `gcm_inplace_normal_use`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.008562 INFO  Encrypting 445 bytes: 10148 cycles
└─ test::tests::gcm_inplace_normal_use @ tests/test.rs:1864
0.008905 INFO  Decrypting 445 bytes: 10128 cycles
└─ test::tests::gcm_inplace_normal_use @ tests/test.rs:1887
0.008935 INFO  (14/14) running `gcm_inplace_all_sizes`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
0.008957 DEBUG 0-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009002 DEBUG 1-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009057 DEBUG 2-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009113 DEBUG 3-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009169 DEBUG 4-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009225 DEBUG 5-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009283 DEBUG 6-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009342 DEBUG 7-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009401 DEBUG 8-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009460 DEBUG 9-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009520 DEBUG 10-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009581 DEBUG 11-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009642 DEBUG 12-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009704 DEBUG 13-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009766 DEBUG 14-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009830 DEBUG 15-length buffer
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1900
0.009894 DEBUG 0-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.009936 DEBUG 1-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.009985 DEBUG 2-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010035 DEBUG 3-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010084 DEBUG 4-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010133 DEBUG 5-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010183 DEBUG 6-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010232 DEBUG 7-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010282 DEBUG 8-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010332 DEBUG 9-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010383 DEBUG 10-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010433 DEBUG 11-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010484 DEBUG 12-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010534 DEBUG 13-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010585 DEBUG 14-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010636 DEBUG 15-length AAD
└─ test::tests::gcm_inplace_all_sizes @ tests/test.rs:1915
0.010688 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:1491
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p rng-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling ppv-lite86 v0.2.10
   Compiling rand_chacha v0.3.1
   Compiling rng-testsuite v0.1.0 (/tmp/tmpt34obq9z/rng-testsuite)
    Finished test [optimized + debuginfo] target(s) in 2.46s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-c767ac65602b86db)
(HOST) INFO  flashing program (36.82 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/2) running `cha_cha`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:31
 WARN  Test results are only valid for release mode
└─ test::tests::cha_cha @ tests/test.rs:47
 INFO  ChaCha20: 2817.39
└─ test::tests::cha_cha @ tests/test.rs:91
 INFO  ChaCha12: 1737.995
└─ test::tests::cha_cha @ tests/test.rs:92
 INFO  ChaCha8: 1199.65
└─ test::tests::cha_cha @ tests/test.rs:93
 INFO  HW: 409.915
└─ test::tests::cha_cha @ tests/test.rs:94
 INFO  (2/2) running `random_enough_for_me`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:31
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:31
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p rtc-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling rtc-testsuite v0.1.0 (/tmp/tmpt34obq9z/rtc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.39s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-bfb705fa412c01af)
(HOST) INFO  flashing program (17.86 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000010 INFO  (1/3) running `test_set_date_time_lse`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.160256 TRACE four_rtc_clk_cycles=5856
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.170546 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>007 Δ 7
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.170582 INFO  (2/3) running `test_set_date_time_lsi`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.170931 TRACE four_rtc_clk_cycles=6000
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.181227 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>009 Δ 9
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.181263 INFO  (3/3) running `test_set_date_time_hse`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
0.181488 TRACE four_rtc_clk_cycles=192
└─ test::test_set_date_time_with_clk @ tests/test.rs:39
0.191567 DEBUG Timestamp before<PHONE_NUMBER>000 after<PHONE_NUMBER>010 Δ 10
└─ test::test_set_date_time_with_clk @ tests/test.rs:84
0.191603 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:93
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p rcc-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling rcc-testsuite v0.1.0 (/tmp/tmpt34obq9z/rcc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.41s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-b944c20e483c3ba4)
(HOST) INFO  flashing program (13.90 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
 INFO  (1/3) running `sysclk_switching`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
 INFO  from Hsi to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hsi to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_0) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Hse(V1_2) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range200k) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range400k) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range800k) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range1M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range2M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range4M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range8M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range16M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range24M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range32M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Hsi
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Hse(V1_0)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Hse(V1_2)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range200k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range400k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range800k)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range1M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range2M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range4M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range8M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range16M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range24M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range32M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  from Msi(Range48M) to Msi(Range48M)
└─ test::tests::sysclk_switching @ tests/test.rs:117
 INFO  (2/3) running `enter_exit_lprun`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
 INFO  Range200k
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  Range400k
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  Range800k
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  Range1M
└─ test::tests::enter_exit_lprun @ tests/test.rs:136
 INFO  (3/3) running `lsi_to_from`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
 INFO  LSI disabled from Div1 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI disabled from Div1 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI disabled from Div128 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI disabled from Div128 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:179
 INFO  LSI enabled from Div1 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 INFO  LSI enabled from Div1 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 INFO  LSI enabled from Div128 to Div1
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 INFO  LSI enabled from Div128 to Div128
└─ test::tests::lsi_to_from::{{impl}}::format @ tests/test.rs:191
 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:92
────────────────────────────────────────────────────────────────────────────────
(HOST) INFO  device halted without error

Output from: cargo test -p adc-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
   Compiling adc-testsuite v0.1.0 (/tmp/tmpt34obq9z/adc-testsuite)
    Finished test [optimized + debuginfo] target(s) in 0.58s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-25ac4abb6638d544)
(HOST) INFO  flashing program (20.37 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/10) running `enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000034 INFO  Enable cycles: 137 CPU 34 ADC
└─ test::tests::enable @ tests/test.rs:80
0.000067 INFO  Disable cycles: 105 CPU 26 ADC
└─ test::tests::enable @ tests/test.rs:99
0.000099 INFO  (2/10) running `tsen_enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000375 INFO  (3/10) running `vbat_enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000402 INFO  (4/10) running `vref_enable`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000428 INFO  (5/10) running `vref`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000536 INFO  vref_cal: 1508
└─ test::tests::vref @ tests/test.rs:187
0.000557 INFO  vref pre-calibration: 1529 Δ 21
└─ test::tests::vref @ tests/test.rs:190
0.000585 INFO  vref post-calibration: 1499 Δ 9
└─ test::tests::vref @ tests/test.rs:191
0.000613 INFO  (6/10) running `test_hsi16`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000703 INFO  vref: 1499 Δ 9
└─ test::tests::test_hsi16 @ tests/test.rs:216
0.000737 INFO  (7/10) running `temperature`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.000948 INFO  Temperature: 31 °C
└─ test::tests::temperature @ tests/test.rs:235
0.000970 INFO  (8/10) running `vbat`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.001056 INFO  VBAT=1371 Δ 6
└─ test::validate_vbat @ tests/test.rs:31
0.001085 INFO  (9/10) running `vbat_advanced`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.001147 INFO  Calibration cycles: CPU 470 ADC 117
└─ test::tests::vbat_advanced @ tests/test.rs:269
0.001178 INFO  Enable cycles: CPU 120 ADC 30
└─ test::tests::vbat_advanced @ tests/test.rs:280
0.001207 INFO  Channel configuration cycles: CPU 15 ADC 3
└─ test::tests::vbat_advanced @ tests/test.rs:292
0.001252 INFO  Sample cycles: CPU 717 ADC 179
└─ test::tests::vbat_advanced @ tests/test.rs:305
0.001281 INFO  VBAT=1372 Δ 7
└─ test::validate_vbat @ tests/test.rs:31
0.001309 INFO  VBAT=1372 Δ 7
└─ test::validate_vbat @ tests/test.rs:31
0.001338 INFO  (10/10) running `stop_conversion`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
0.001367 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:35
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p subghz-testsuite --target thumbv7em-none-eabi -- --probe<PHONE_NUMBER>53500A20393256
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
   Compiling static_assertions v1.1.0
   Compiling nucleo-wl55jc-bsp v0.1.0-alpha.0 (/tmp/tmpt34obq9z/nucleo-wl55jc-bsp)
   Compiling subghz-testsuite v0.1.0 (/tmp/tmpt34obq9z/subghz-testsuite)
    Finished test [optimized + debuginfo] target(s) in 1.06s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-fbb389608b5f5d95)
(HOST) INFO  flashing program (26.42 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/5) running `buffer_io`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.000406 INFO  Cycles 255B: 17970
└─ test::tests::buffer_io @ tests/test.rs:329
0.000512 INFO  Cycles 0B: 1186
└─ test::tests::buffer_io @ tests/test.rs:338
0.000533 INFO  (2/5) running `buffer_io_no_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.002244 INFO  Cycles 255B: 80994
└─ test::tests::buffer_io_no_dma @ tests/test.rs:351
0.002354 INFO  Cycles 0B: 1351
└─ test::tests::buffer_io_no_dma @ tests/test.rs:360
0.002376 INFO  (3/5) running `sleep_enter_exit`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.004473 INFO  74839 cycles to wake radio
└─ test::tests::sleep_enter_exit @ tests/test.rs:375
0.004511 INFO  (4/5) running `fsk_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.017487 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:177
0.017517 DEBUG RX with timeout 276 ms
└─ test::ping_pong @ tests/test.rs:186
0.181346 INFO  RX done
└─ test::ping_pong @ tests/test.rs:209
0.181387 INFO  Ok(FskPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    preamble_err: false,
    sync_err: false,
    addr_err: false,
    crc_err: false,
    length_err: false,
    abort_err: false,
    pkt_received: true,
    pkt_sent: false,
    rssi_sync: -37,
    rssi_avg: -36,
})
└─ test::ping_pong @ tests/test.rs:214
0.181538 INFO  received PING
└─ test::ping_pong @ tests/test.rs:229
0.189803 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.198051 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.206301 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.214548 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.222798 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.231045 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.239295 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.247546 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.255797 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.264050 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.264066 INFO  (5/5) running `lora_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.277149 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:177
0.277261 DEBUG RX with timeout 127 ms
└─ test::ping_pong @ tests/test.rs:186
0.416465 INFO  RX done
└─ test::ping_pong @ tests/test.rs:209
0.416506 INFO  Ok(LoRaPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    rssi_pkt: -36,
    snr_pkt: 13,
    signal_rssi_pkt: -39,
})
└─ test::ping_pong @ tests/test.rs:215
0.416630 INFO  received PING
└─ test::ping_pong @ tests/test.rs:229
0.480535 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.544424 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.608329 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.672234 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.736146 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.800065 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.863991 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.927922 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.991856 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
1.055804 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
1.055820 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error

Output from: cargo test -p subghz-testsuite --target thumbv7em-none-eabi -- --probe 0034001A5553500B20393256
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on build directory
    Finished test [optimized + debuginfo] target(s) in 1.06s
     Running tests/test.rs (target/thumbv7em-none-eabi/debug/deps/test-fbb389608b5f5d95)
(HOST) INFO  flashing program (26.42 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
0.000007 INFO  (1/5) running `buffer_io`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.000406 INFO  Cycles 255B: 17970
└─ test::tests::buffer_io @ tests/test.rs:329
0.000512 INFO  Cycles 0B: 1186
└─ test::tests::buffer_io @ tests/test.rs:338
0.000533 INFO  (2/5) running `buffer_io_no_dma`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.002244 INFO  Cycles 255B: 80994
└─ test::tests::buffer_io_no_dma @ tests/test.rs:351
0.002354 INFO  Cycles 0B: 1351
└─ test::tests::buffer_io_no_dma @ tests/test.rs:360
0.002376 INFO  (3/5) running `sleep_enter_exit`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.004458 INFO  74106 cycles to wake radio
└─ test::tests::sleep_enter_exit @ tests/test.rs:375
0.004495 INFO  (4/5) running `fsk_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.017826 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:177
0.017857 DEBUG RX with timeout 117 ms
└─ test::ping_pong @ tests/test.rs:186
0.161615 INFO  RX timeout 143 ms Δ 26 ms
└─ test::ping_pong @ tests/test.rs:197
0.181323 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.181337 INFO  Attempt: 1/100
└─ test::ping_pong @ tests/test.rs:177
0.181449 DEBUG RX with timeout 52 ms
└─ test::ping_pong @ tests/test.rs:186
0.190169 INFO  RX done
└─ test::ping_pong @ tests/test.rs:209
0.190210 INFO  Ok(FskPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    preamble_err: false,
    sync_err: false,
    addr_err: false,
    crc_err: false,
    length_err: false,
    abort_err: false,
    pkt_received: true,
    pkt_sent: false,
    rssi_sync: -34,
    rssi_avg: -34,
})
└─ test::ping_pong @ tests/test.rs:214
0.190361 INFO  received PONG
└─ test::ping_pong @ tests/test.rs:240
0.190376 INFO  (5/5) running `lora_ping_pong`...
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
0.203822 INFO  Attempt: 0/100
└─ test::ping_pong @ tests/test.rs:177
0.203851 DEBUG RX with timeout 111 ms
└─ test::ping_pong @ tests/test.rs:186
0.341093 INFO  RX timeout 137 ms Δ 26 ms
└─ test::ping_pong @ tests/test.rs:197
0.416596 INFO  TX done
└─ test::tx_or_panic @ tests/test.rs:108
0.416610 INFO  Attempt: 1/100
└─ test::ping_pong @ tests/test.rs:177
0.416721 DEBUG RX with timeout 269 ms
└─ test::ping_pong @ tests/test.rs:186
0.482175 INFO  RX done
└─ test::ping_pong @ tests/test.rs:209
0.482216 INFO  Ok(LoRaPacketStatus {
    status: Status { mode: Ok(StandbyHse), cmd: Ok(Avaliable) },
    rssi_pkt: -33,
    snr_pkt: 14,
    signal_rssi_pkt: -35,
})
└─ test::ping_pong @ tests/test.rs:215
0.482340 INFO  received PONG
└─ test::ping_pong @ tests/test.rs:240
0.482355 INFO  all tests passed!
└─ test::tests::__defmt_test_entry @ tests/test.rs:271
────────────────────────────────────────────────────────────────────────────────
  (HOST) INFO  device halted without error


RegExps are broken when made immutable

I expect these two pieces of code to yield the same result:
/ABC/.test("ABC")
// => true

Immutable({regexp: /ABC/}).regexp.test("ABC")
// => TypeError:  Immutable(...).regexp.test is not a function

but they do not.
Ideally, seamless-immutable should not break regular expressions. If that is not possible because they are inherently mutable (as I suspect) that it should perhaps not just silently break them.
Possible courses of action (not complete, not exclusive):

Make RegExp work! (likely impossible because they are mutable by nature)
Warn when trying to Immutable-ize something that would be broken by it (such as RegExp or e.g. Node https.Agent)
Or deny to do so and just throw an error (that is likely too aggressive)
Enable the user to provide a custom "converters" to handle these special cases, e.g. something like: Immutable(objWithRegExps, { "RegExp": (v) => v /* return unmodified, i.e. mutable*/}) and then, somewhere in the code, if (customConverters[current.constructor.name]) return customConverters[current.constructor.name](current);

Thoughts / advice?

RegExp is immutable by default as far as I understand it.
var a = new RegExp('a')

a.flags
// ""
a.flags = 'g'
// "g"
a.flags
// "" (still empty)

a.source
// "a"
a.source = 'b'
// "b"
a.source
// "a"

This issue is also present with Errors - which is how I found my way here.
Perhaps a solution like that in #31?

I just looked into this in more depth and I realized it should be closed as a duplicate of https://github.com/rtfeldman/seamless-immutable/issues/124

@rtfeldman So this is duplicate of #124 but that was closed with "won't fix" with the explanation that Immutable should only store plain old data - i.e. that regular expressions, Errors etc. can not be included in an Immutable data structure. Correct?
Perhaps, if that is the case, it should be clearly documented in the README and, even better, an exception should be thrown when trying to include any other then supported type of data (i.e. fail quickly and with a clear error message then later with a mysterious error). What do you think?
Also, according to the README, it is possible to include "mutable" elements of type Date, function, React component. That provides a simple workaround: instead of using prop: RegExp(..), I could use () => new RegExp(). But wouldn't it be even better to expand this and allow the user to define what "mutable" data can be part of an Immutable data structure? Something like I proposed in 4. above or something similar (a list of types/paths to leave as they are ...).
Thoughts?


Stop banner text from running full width

Before

After

@edds / @gemmaleigh / @markhurrell is 2/3 our standard text column width?

@gemmaleigh is this superseded by #201?

Closing in favour of #201


maneuver is disabled

Foundry 0.8.9
GURPS Game Aid 0.12.3
I just can't set a maneuver for a character token.
Right click on the token then clicking on any of the maneuver don't do anything

maneuver dropdown is disabled on conditions section

Either way there are no logs on Developer Console

@josmardias Make sure your combat is on an active scene.
I had the same issue and noticed that it works when the combat is on the active scene, but does not on deactivated scenes.

Oh, didn't test on the active scene yet, but you are probably right cause I clearly remember testing on a scene that was not active.
Thanks for the help, that was quick!
On that same subject, I assume we are looking for the active scene as source of truth for "which tokens are involved in the combat". Shouldn't we just check the combat tracker then?
Anyway I'll test it in a bit but that fixes it for me so I'm closing the issue, I can reopen it later if I find more problems. Thanks again!


Reduce test warnings

In reference to #1074, this PR aims to reduce test warnings. Some warnings might need further treatment to mitigate/suppress them but this implementation fixes some of the obvious ones.
Thanks!

I am sorry for a bunch of small pushes..

I am sorry for a bunch of small pushes..

As you say, there are still some warnings left but this is strictly better than before. Thanks a lot!

As you say, there are still some warnings left but this is strictly better than before. Thanks a lot!

Thanks @astrojuanlu! Yes, those warnings which include ERFA, Orbit.pqw would need further treatment but can be dealt in the future too!
Thanks!!

Thanks @astrojuanlu! Yes, those warnings which include ERFA, Orbit.pqw would need further treatment but can be dealt in the future too!
Thanks!!


enable beacon plugin test

What was wrong?
The test has been disabled for a long time
How was it fixed?
Create a genesis file then run the beacon plugin
Cute Animal Picture

The plan was to experiment on pylibp2p and could break the beacon chain plugin temporarily. So no need the test now


A problem about subscript and superscript in QtWebKit4

I downloaded the latest KaTeX and use it in a web browser developed by me.
But I found there is a problem about subscript and superscript like the following picture:

$$
\begin{aligned}
a_i \\
b_j^2 \\
c^2
\end{aligned}
$$

Looks very bad, isn't it?
Can someone tell me how to fix that problem by modifying KaTeX sources?Thx>_<
Sorry for my bad English.

I suspect this is either quirks mode or a failure to load the CSS file (and thus the fonts). Can you confirm that you're loading katex.min.css, and that you're using <!DOCTYPE html>?

@edemaine
yeah, I'm pretty sure I have loaded katex.min.css and used <!DOCTYPE html>.

@iwtwiioi We'll need more information to help you here. The example renders fine in the demo page.

@edemaine
On Windows 10, the problem exists:
Environment:
Python 3.4.4 (v3.4.4:737efcadf5a6, Dec 20 2015, 20:20:57) [MSC v.1600 64 bit (AMD64)] on win32
PySide 1.2.4, installed by command pip install pyside --only-binary :all:
KaTex, the latest version, released on 08 Aug
Here is another example:

made by $$ans=|S|-|A_i|+\sum_{i < j} |A_i \cap A_j|-...+ |A_1 \cap A_2 \cap A_3 \cap A_4|$$
On Linux, every thing is ok.
My project home:

I guess I'm confused why you think this is a bug with KaTeX, instead of a bug with your custom web browser, given that these examples render fine in Chrome, and not in your web browser...

Looks like a duplicate of #45.  The problem seems to be with vlists that use shifts.  The \sum_{i < j} layout doesn't use shift in the vlist while all of the subscripts do.

@edemaine
I didn't say this is a bug with KaTeX, I just want to ask for a way to modify the KaTeX's sources to satisfy my browser...QAQ

I would suggest you to upgrade to Qt 5, because WebKit in Qt 4 is rather quite outdated.

Closing this barring further information. Let us know the result of upgrading to Qt 5.


Fixes non-uniform scaling of normals

For meshes with non-uniform scaling, we now use the transpose of the inverse of the transformation matrix.
Fixes: https://github.com/godotengine/godot/issues/51986

Thanks.


edit metadata takes forever to load

i believe this has been reported for a few dandisets.  here is an example dandiset, which has minimal metadata. https://gui.dandiarchive.org/#/dandiset/000043
i know it loads for some and is not related to size of the metadata (for e.g., i was able to edit metadata for dandiset 26 just fine).
this also relates to the more automated testing issue of being able to hit the edit metadata button in our tests.

the issue has to do with values that do not correspond to the schema. in general we should prevent this from happening at the API level.  i fixed the usability issue temporarily by fixing the relevant piece of metadata (in this case these were orcid identifiers that did not get parsed properly by the metadata converter.
however, i will leave this open for now since we don't have validators in the API, and someone, although unlikely, could potentially use the API to update metadata.

FWIW it (browser) even times out for me locally and @jwodder in selenium (https://github.com/dandi/dandi-api-webshots/issues/1#issuecomment-831918453)  on https://gui.dandiarchive.org/#/dandiset/000021

thanks for the report, will look at the metadata, probably some identifiers are of. we did not do json schema check when we uploaded the metadata and that's probably what's broken.

while it is broken - might be a good time to fix up the UI part so it doesn't just hang but rather returns error or smth like that (ref: https://github.com/dandi/dandiarchive/issues/613)

while it is broken - might be a good time to fix up the UI part so it doesn't just hang but rather returns error or smth like that (ref: #613)

This might not be so easy, but I could attempt it. The problem is that the UI has to decide to either entirely allow or disallow the meditor to be opened. This could be approached by running json schema validation with a separate tool (probably ajv), and if it fails, don't show the meditor. However we explicitly allow invalid metadata until publish, so we'd maybe have to only care about specific kinds of validation errors.

This is also separate from #613, as this is a client side bug, with no connection to the API.

Correct in that unrelated to dandi-api, but IMHO there should be a generic/unified way to channel an error message to the web ui user.

the particular metadata is fixed. but we should run through the check on all the metadata. i think to simplify things the job of the UI should not be to check validity of metadata. it can do so, but we need to ensure that the API server serves up and ingest valid metadata. the word "valid" as we have discussed earlier has several levels. in the current instance of issues we are seeing, it is not about missing metadata, but when metadata values are incorrect.
what the ui will however have to do is to ensure that the metadata and schema version go hand  in hand and support multiple schema versions for both landing page and editing.

is this still a valid issue?

I think this can be closed. Others can reopen if there are still things to do here.


The installation log is missing

Describe the version
version about:

kubean
v0.4.2-rc3-23-gfa9d3050
kubespray
kubenetes
v1.23.1
what CNI and itsversion

Describe the bug
A clear and concise description of what the bug is.
Create a cluster by kubean. After 27 minutes, the logs disappear. Execute kubectl logs - xxx - nkubean-system to view there are no logs. The logs are retained for about 20 minutes.
How To Reproduce
Steps to reproduce the issue:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots and log
If applicable, add screenshots and log to help explain your problem.

Additional context
Add any other context about the problem here.

/kind bug

/kind test

Problems that cannot be reproduced


Configuration failure

Right, so... I toss in the png, background.png, into the requisite folder, it's 1920x1080 in size. I use an existing config file, all looks good except the text along the bottom is cut off. So I go into Infranview and scale the image down to 1520x855, so Infranview can display it with no zoom and it fits the screen perfectly. Nope, same thing, same amount of text at the bottom is cut off. I go into the config json, change the mode from 'fill' to 'center' and now the text top and bottom is completely gone off screen. For giggles I put in the height and width parameters under mode and no go, same deal. How in the heck do I get this image to not go off screen but remain fully on screen? The config I copied from the background.png was a lot bigger and it fit fine so I am at a complete loss. O.o

The config for the images sometimes a bit confusing. You can try to import it as texture or as image. You can tinker a bit around with the "width", "height", "imageHeight" and "imageWidth" variables. I also get sometimes weird results but most of the time it get it working with a tial and error method and the 4 variables.


"tfupdate provider" to upgrade to latest minor version instead of major version.

What problem are you facing?
I would like to use
tfupdate provider <providername> to upgrade to the latest minor version of a provider. current behavior is that "tfupdate provider" will upgrade to the latest version even when this is a major upgrade (with possible breaking changes).
How could pre-commit-terraform help solve your problem?
Would be nice if the pre-commit hook implements some kind of version constraint,
Example mockup code:
- id: tfupdate
        name: Autoupdate google provider version
        args:
          - --constraint="version<4.0.0"
          - --args=provider google

so that tfupdate command would upgrade to latest 3.X.X version but not to google provider version 4.X.X

I'm not quite sure I understood the description of desired problem resolution, though I'd like to admit that pre-commit-terraform is a thin wrapper for tfupdate among other tools and it doesn't provide any extended functionality that is not provided by the tool itself.
You actually can pass any args supported by tfupdate to the hook: https://github.com/antonbabenko/pre-commit-terraform#tfupdate
What you probably are looking for is -v  --version      A new version constraint (default: latest): https://github.com/minamijoyo/tfupdate#provider

Thanks @yermulnik
after a discussion with the author of tfupdate and some testen i found the right solution
here is an example of a terraform version update and a provide update (in the existing terraform code) ... without accidently upgrading to the next major update.
      - id: tfupdate
        name: Autoupdate Terraform version
        args:
          - --args=terraform
          - --args=--version="~> 1.6"
      - id: tfupdate
        name: Autoupdate google provider version
        args:
          - --args=provider google
          - --args=--version="~> 5"


FingerTip Dataset Format

Hi @tucan9389 ,
I am working on a project that requires finger tracking. I hope you don't mind me asking you a couple of basic questions. I would like to use only 1 keypoint ("FingerTip") during training, and I am using the annotation tool from "don't be turtle" project to create my own dataset.
Did you use "background" images in your training set? I mean, did you have images without any index finger in them (just background)?
If so, would you mind sharing with me one example of how the keypoints were annotated in your training set (i.e., what values you set in the keypoints lists)?
Thanks a lot
Cheers

Hi @Lisandro79

Did you use "background" images in your training set? I mean, did you have images without any index finger in them (just background)?

No. I took videos using my iPhone and split to images. The split images contain various background. And I just annotate only 1 keypoint (Fingertip. The endpoint of the index finger) for all split images.

If so, would you mind sharing with me one example of how the keypoints were annotated in your training set (i.e., what values you set in the keypoints lists)?

When I find the fingertip dataset, I'll share it (maybe for not total, but partial). But I can't guarantee when to share.
Thank you
Cheers

Thanks a lot for your fast response. I did not mean to share your dataset, I was just curious on how to annotate a "background" image in COCO format.
I thought of using "FingerTip": [0, 0, 0] for the "background" images. However, I think (still need to test it) this might give me problems with the loss function during training (e.g., if a batch of images contains only images without finger tips then all images might be not considered for adjusting the gradients due to the visibility label "0").
I will try and see how it goes.
Thanks a lot again


Field not validated when using Decimal(as_string=True)

When we do something like this
'value': fields.Decimal(required=True, as_string=True),
With this as input:
{ "value": 123.2, ... }
Webargs does not throw a 422 unprocessible entity error. We're using python flask, sqlalchemy and marshmallow, and we've looked all over at our code. Is it possible that this is an issue with webargs?
Thanks

as_string only affects serialization behavior, not validation/deserialization. See https://marshmallow.readthedocs.org/en/latest/api_reference.html#marshmallow.fields.Decimal . If you want to validate that the input must be a string, you could create a custom field that subclasses marshmallow.fields.Decimal.


gulp-data cannot work well with gulp-pug

Following the document of gulp-data, I tried to inject some variables into my pug template, but nothing happend.No data was injected and no errors in console.
Then I use 'gulp-jade' instead of 'gulp-pug', the problem has gone.
pug template:
div= foo

gulpfile.js
const data = require('gulp-data')
const pug = require('gulp-pug')
// const pug = require('gulp-jade') // If I use this, everything will work well.
gulp.task('pug', e => gulp.src('./src/pug/index.pug')
  .pipe(data(function (file) {
    return {foo: 'bar'}
  }))
  .pipe(pug())
  .pipe(gulp.dest('./dist/'))
)

I will take a look, thanks.

This will be introduced in the next version (after I fix the other issues).  Thank you.  :)

Released that new version a little while ago by the way.  Should work now.

Thank you for your great work!


Error on notification jumpDefinition

As mentioned in another issue (#19) the "go to definition" command doesn't work. As suggested I did some logging
and (hopefully) attached the log file:
coc-perl.log
Funny, it says the language server doesn't support it, though it certainly should (and the server installation worked without error)

Also pasted the contents to https://l.perl.bot/

Also pasted the contents to https://l.perl.bot/

You pasted the direct link to the perlbot instead of your pasted content :P Can you try it again?
The coc-perl.log file worked and I can see that coc-perl was launched just fine, but something might have broke during server runtime, thus reporting the "jumpDefinition" error. The other log will give more insights.

Sorry I don't understand. I pasted the exact same contents into the text field that is also in the attachment.
I did not paste just a link but the text you already got. This is why I also don't understand why you need it twice.
I think I did exactly what you told me

open coc-perl.log in vim
copy the contents to the clipboard
open https://l.perl.bot/ in browser
past the clipboard into the text field
click submit

As I said it is the same log contents you got in the coc-perl.log. Sorry again but what else can I do? I do not have other contents than that in coc-perl.log but I really didn't paste just a link.
I am really puzzeled, sorry.
Also: the perl bot seems to expect perl code. But the log file contens is just plain text, no code ?!? Or should I paste my test script? But how can the perl bot connect to my language server?

I think I know now what contents you mean. I pasted it into the text field within the perl bot but it is still complaining after the commit about missing semicolons which is understandable because it is log contents, not perl code.
Since I obviously do not know what really happens on perl bot, what if I just send you the log file as an email attachment?

Perhaps this one helps: https://l.perl.bot/p/leamif ?

Perhaps this one helps: https://l.perl.bot/p/leamif ?

Yes!! This data! :-D @bukephalos, I should've explained better, sorry. It's indeed the content I was expecting :)
Also, to avoid the Perl errors in the perl bot you can just change the "language" drop-down menu to plaintext.
However, I was expecting errors, but things seems fine.
Can you try once again to generate a new log?

close all Perl files open in vim/neovim
erase the log file
open the test file
move to something() line and press gd.
copy log file contents to perl bot and give me the link :)

Another try: https://l.perl.bot/p/lkhnqo
This time I made sure :CocOpenLog shows the error ("definition provider not found for current buffer")

Things are really odd.

is it possible that the whole call is ignored for whatever reason when logging is enabled???

No, the logging has no effect on the results of an operation.

[coc.nvim]: Error on notification "jumpDefinition": definition provider not found for current buffer, your language server doesn't support it.

This error happens when the language server underneath isn't running for some reason (or if the server doesn't support the operation, which isn't true in our case).
But ok, lets try something else:

Can you confirm the coc.nvim version you are using (:CocInfo)?
Can you confirm the Perl::LanguageServer version you have installed (cpan -D Perl::LanguageServer)?
Can you paste here, or send a new file of :CocOpenLog you tested in the other machine (VM) where you had the same issue?

Things are really odd.

Indeed. Thanks for your patience!
I also noticed what you identitied as a typo but attributed it to a cut and paste issue. After all the syntax check works and it also has to call run, doesn't it?
Also I doubt that it really is a coc-nvim/coc-perl issue since I got the same problem in VScode. This is why I tried (on the Ubuntu VM) to downgrade Perl::LanguageServer to 2.4.0 but with the same result.

But ok, lets try something else:
1. Can you confirm the coc.nvim version you are using (`:CocInfo`)?

coc.nvim version: 0.0.82-b7375d5f 2023-01-30

2. Can you confirm the Perl::LanguageServer version you have installed (`cpan -D Perl::LanguageServer`)?

G/GR/GRICHTER/Perl-LanguageServer-2.5.0.tar.gz (with the first commit of your fix applied by hand)

3. Can you paste here, or send a new file of `:CocOpenLog` you tested in the other machine (VM) where you had the same issue?

This VM I downgraded to 2.4.0 (s. --version). The run looks fine:
2023-07-11T17:23:55.324 INFO (pid:257999) [extension:coc-perl] - extension "perl" is now active
  2023-07-11T17:23:55.324 INFO (pid:257999) [extension:coc-perl] - try if port 13603 is available
  2023-07-11T17:23:55.329 INFO (pid:257999) [plugin] - coc.nvim initialized with node: v18.16.1 after ^[[33m223^[[39m
  2023-07-11T17:23:55.330 INFO (pid:257999) [extension:coc-perl] - use 13603 as debug adapter port
  2023-07-11T17:23:55.330 INFO (pid:257999) [extension:coc-perl] - cmd: perl args: -MPerl::LanguageServer -e Perl::LanguageServer::run -- --log-level 2 --log-file /tmp/coc-perl.log --version   2.4.0 --port 13603
  2023-07-11T17:23:55.395 INFO (pid:257999) [language-client-index] - Language server "perl" started with 258012
  2023-07-11T17:24:01.536 INFO (pid:257999) [attach] - receive notification: highlight []
  2023-07-11T17:24:04.204 INFO (pid:257999) [attach] - receive notification: jumpDefinition []
  2023-07-11T17:24:04.210 ERROR (pid:257999) [attach] - Error on notification jumpDefinition Error: definition provider not found for current buffer, your language server doesn't support it.
      at Rb.checkProvider ^[[90m(/home/ansible/^[[39m.vim/pack/coc/start/coc.nvim/build/index.js:281:34291^[[90m)^[[39m
      at gb.request ^[[90m(/home/ansible/^[[39m.vim/pack/coc/start/coc.nvim/build/index.js:269:5370^[[90m)^[[39m
  ^[[90m    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)^[[39m
      at async gb.gotoDefinition ^[[90m(/home/ansible/^[[39m.vim/pack/coc/start/coc.nvim/build/index.js:269:6781^[[90m)^[[39m
      at async _b.cocAction ^[[90m(/home/ansible/^[[39m.vim/pack/coc/start/coc.nvim/build/index.js:281:46242^[[90m)^[[39m
      at async EventEmitter.<anonymous> ^[[90m(/home/ansible/^[[39m.vim/pack/coc/start/coc.nvim/build/index.js:281:47836^[[90m)^[[39m
  2023-07-11T17:24:04.508 INFO (pid:257999) [attach] - receive notification: highlight []
  2023-07-11T17:24:13.337 INFO (pid:257999) [attach] - receive notification: openLog []

@bukephalos are you trying to open a file in the same directory you're cded? For instance:
$ cd test/perl/
$ nvim test.pl

or are you trying to open the file somewhere else? Like:
$ pwd
/home/bmeneg/
$ nvim test/perl/test.pl

I was able to "partially" reproduce the error you're seeing, when editing a file outside the workdir I'm currently in.

I would even ask if you don't have anything in your @INC path that could interfere, so coc-perl could be calling a different version of language server. But you tested in another machine, so it should not have the same issue.

Still possible since I have quite a software stack I install on most of my systems. Could be the same trouble maker on both. I once had a really long debugging session where the problem only appeared with a specific version of the "Want" module that was somewhere deep within the dependency chain.
I still have a laptop I can try and perhaps set up a totally clean VM (will take some time)

@bukephalos are you trying to open a file in the same directory you're cded? For instance:
$ cd test/perl/
$ nvim test.pl

or are you trying to open the file somewhere else? Like:
$ pwd
/home/bmeneg/
$ nvim test/perl/test.pl

I was able to "partially" reproduce the error you're seeing, when editing a file outside the workdir I'm currently in.

I am using plain vim not nvim and doing the first case (first cd then open without a path:
cd
vim test.pl

And as I said, it also happens in VScode but there only with my test script, it works within the Perl::LanguageServer source code

I still have a laptop I can try and perhaps set up a totally clean VM (will take some time)

No need, I might have an idea on what's happening.

it works within the Perl::LanguageServer source code

Does it?! And in your test code it isn't? hahaha.. ok.. I'll check something, might take some time though.

@bukephalos, hi again.
If you move your test.pl to any other folder other than your home dir, something like cd && mkdir test/ && mv test.pl test/, then run vim test/test.pl or cd test/ && vim test.pl, does the gd work?

We are getting closer :-)
with "cd test/ && vim test.pl" gd does indeed work!
"vim test/test.pl" still does not work.
gd on a variable still doesn't work in neither variant. Is it supposed to work, too? In the meantime I also did a few tests with PerlNavigator and there it also works with variables.

Ok, so I might have found the culprit, but not sure how to solve yet. The issue is on the server.
And with variables: it should work. At least I was able to get it working when cd test/ && vim test.pl :disappointed:

Here my test script, opened with "cd test && vim test.pl":
!/usr/bin/perl

  use strict;
  use warnings;

  my $somevar = 112;

  dosomething();

  sub dosomething {
      print $somevar;
  }

Then move the cursor on the "s" of "print $somevar;" press "gd" => "definition not found"
gd on "dosomething();" now moves the cursor to the "s" of "sub dosomething".

It just works here, lol.
But wait, lets debug one thing at a time.
First, I'll keep diving into server code to figure out the issue we're seeing when gd'ing from home dir.
Then, we check what's going on with your variable definition goto's.

Addition: just tested with VScode: even after cd test gd doesn't work for subs (the exact test that works with vim).
To make things even more weird (new test):
mkdir /tmp/foobar
cp test.pl /tmp/foobar
cd /tmp/foobar
code .
# also works:

=> both(!) gd variants work (sub and var)
In this variant it also works with vim (both gd)
????????

Do you think there is a chance for a fix or is the only solution to keep the workspace out of the home dir?

@bukephalos I'm really sorry, this week things got a bit crazy around here and had no time to check the fix for this situation. For now, I suggest keeping the workspace out of home dir. But I'll do my best to get a fix for it until/during weekend.

@bukephalos, even though I didn't get to the bottom of this issue, coc-perl now officially support PerlNavigator :-)
Feel free to use it via coc-perl while we don't make Perl::LanguageServer to work correctly.


Include an executed_command attribute in check results

I've caught myself a few times getting hung up on troubleshooting the effects of command token substitution in my check definitions. Check results and events will show the defined check command with the token, but they don't show the command the client actually executes.
In my most recent experience, I was configuring a client to use command token substitution with the check-http.rb plugin, as follows:
{
  "checks": {
    "sensu-website": {
      "command": "check-http.rb -u :::website|https://sensuapp.org:::",
      "subscribers": [
        "documentation"
      ],
      "interval": 60
    }
  }
}

Unfortunately, the check-http.rb plugin doesn't include any information about the url it queries - just the HTTP response code. So I kept having to double check that my configuration was correct. With this PR, that would have been unnecessary, because the output will make it obvious:
$ curl -s http://localhost:4567/results/client-01/sensu_website | jq .
{
  "check": {
    "status": 0,
    "executed_command": "check-http.rb -u http://www.google.com",
    "command": "check-http.rb -u :::website|https://sensuapp.org:::",
    "subscribers": [
      "documentation"
    ],
    "interval": 60,
    "name": "sensu_website",
    "issued":<PHONE_NUMBER>,
    "executed":<PHONE_NUMBER>,
    "duration": 0.454,
    "output": "CheckHttp OK: 200, 19105 bytes\n"
  },
  "client": "client-01"
}

...and my client configuration:
$ curl -s http://localhost:4567/clients/client-01 | jq .
{
  "timestamp":<PHONE_NUMBER>,
  "version": "0.23.0",
  "website": "http://www.google.com",
  "socket": {
    "port": 3030,
    "bind": "<IP_ADDRESS>"
  },
  "subscriptions": [
    "documentation"
  ],
  "environment": "development",
  "address": "<IP_ADDRESS>",
  "name": "client-01"
}

I will be surprised if this hasn't been recommended before, which also means I will not be surprised if there's a perfectly reasonable explanation for not merging this. Looking forward to feedback/input. :smile:

Hrm, @portertech just commented to me offline that it "defeats the point of redacting values if you put your secrets in the open", which could happen if you were using command token substitution to fetch secrets from client configuration.
Client attributes may currently be redacted – preventing them from being logged, and from being included in keepalive results, thus preventing them from being accessible via the API – so there's currently no other possibility for exposure, but my suggested change would change that.
Technically, we could add support for redacting check results, but that seems like an unnecessary processing overhead. I'm going to go ahead and close this as a "won't fix".


ignore mycluster.yaml

WTF? Travis failed
Reading configuration file [scancode/ASF-Release.cfg]...
Scanning files starting at [/home/travis/build/apache/incubator-openwhisk-deploy-kube/tools/travis/../..]...
Scan detected 4 error(s) in 4 file(s):
  [/home/travis/build/apache/incubator-openwhisk-deploy-kube/tools/travis/../../.travis.yml]:
       1: file does not include required license header.
  [/home/travis/build/apache/incubator-openwhisk-deploy-kube/tools/travis/../../docker/docker-pull/pull_images.yml]:
       1: file does not include required license header.
  [/home/travis/build/apache/incubator-openwhisk-deploy-kube/tools/travis/../../helm/values.yaml]:
      62: line has trailing whitespace.
  [/home/travis/build/apache/incubator-openwhisk-deploy-kube/tools/travis/../../kubernetes/package-kafka/kafkapkginstaller.yml]:
      20: line has trailing whitespace.
Scan detected 4 error(s) in 4 file(s):

It looks yaml files need license headers.

merge away sir @dgrove-oss


Makes sure we don't ignore partials assuming those are pure templates

TODO:

[ ] Add tests to cover this scenario

I think partials are easy since they're as pure as it gets, but I don't think anyone is using them now


Do not drop newlines after  or

#59 applied a detail from the html spec:

A single newline may be placed immediately after the start tag of pre and textarea elements. This does not affect the processing of the element.

As html is case insensitive to tag names, it was also applied to <TextArea> or <PRE>.
But... Angle bracket components have been introduced. And <TextArea> is now primarly a component, instead of a <textarea>.
This PR would adjust the html spec implementation to only lowercased textarea and pre tags.

html tags is insensitive, why treat lowercased one differently?

This is not a good solution, I'll propose another one.


Ash dev createsite

Final edit of the modern/SPO deployment script

Script has been looked over by Cole 20/3/20


[Bug]: Shopify CLI mismatches ngrok address for webhooks

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
The webhook address the development app tells shopify to send to should match the current ngrok tunnel open.
Actual behavior
It is sending to a different address. For example I will have an app deployed to https://a003c8addb41.ngrok.io?shop=whateverTheShopNameIs but if I make an order and have the order webhook set up when I check the webhooks in the partner platform they are being sent to https://76e03e16cca8.ngrok.io/api/webhooks
Stack trace
No response
Reproduction steps

Make an app using the cli
add a webhook
trigger the webhook

Operating System
MacOS
Shopify CLI version (check your project's package.json if you're not sure)
3.25.0
Shell
zsh
Node version (run node -v if you're not sure)
v16.13.1
What language and version are you using in your application?
Node

Sometimes the webhooks send to the correct url so not sure why it occasionally works properly