Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Call for Tock 2.2 Release Testing #4272

@lschuermann

Description

@lschuermann

We just tagged a release candidate for Tock 2.2, and it's ready for testing!

As discussed in #3197, we're changing our testing strategy starting with this release. Instead of trying to test all boards, we will primarily focus on Tier 1 boards, and specifically the nRF52840DK which we already test as part of our new "Treadmill" hardware CI system. These efforts should allow us to more frequently test & release Tock's "core" components, without placing as large of a burden on maintainers and board contributors.

That said, we don't want to discourage anyone from testing! We'll use this issue for tracking these efforts, which supersedes #3197. If you find yourself with some time and a board on your hands, feel free to copy the "test comment template" below and post your results in a comment to this issue.

Assuming that we don't find any issues or receive requests to extend the testing period, I plan to tag a release some time around Jan 3rd.

Changes in Tock 2.2

Over the next week I will compile a more complete changelog. In the meantime, from the release notes:

With almost two years since Tock 2.1.1, it's about time for a new Tock release! Compared to 2.1.1, this release will contain 3882 commits made in 836 PRs by 90 contributors (of which 48 are new contributors!). This release is the first to support stable Rust for out-of-tree and (a subset of) the in-tree boards, adds new supported boards, and contains many other fixes and improvements. Some notable bug fixes are in the Cortex-M arch crate to prevent userspace applications from executing in privileged mode, and disabling unused PMP regions on RISC-V. A full change list will be included with the final release notes.

Misc Release Todo

Post-release todo:

Test Boards

Tier 1:

Others:

Test Comment Template

Template:
  • Tests run on most Boards

    • examples/sensors
    • examples/c_hello and examples/tests/printf_long
    • examples/tests/console_recv_short and examples/tests/console_recv_long
    • examples/blink
    • examples/rot_client and examples/rot_service
    • examples/blink and examples/c_hello and examples/buttons
    • examples/lua-hello
    • examples/tests/console_timeout
    • examples/tests/malloc_test01
    • examples/tests/stack_size_test01
    • examples/tests/stack_size_test02
    • examples/tests/mpu_stack_growth
    • examples/tests/mpu_walk_region
    • examples/tests/multi_alarm_test
    • examples/tests/adc
    • examples/tests/adc_continuous
    • examples/tutorials/05_ipc/led and examples/tutorials/05_ipc/rng and examples/tutorials/05_ipc/logic
  • nRF specific

    • examples/ble_advertising
    • examples/ble_passive_scanning
  • Imix-specific

    • examples/tests/imix
    • examples/services/ble-env-sense and examples/services/ble-env-sense/test-with-sensors
    • examples/ble-uart
    • examples/ip_sense: Application that samples a sensor and puts it in a UDP broadcast segment
    • examples/tests/udp/udp_send: sends a UDP datagram to a destination port:
    • examples/tests/udp_receive: receives datagrams on a port an blinks when received: pair with udp_send
    • In-Kernel Tests
      • boards/imix/src/test/aes_ccm_test.rs
      • boards/imix/src/test/aes_test.rs
      • boards/imix/src/test/icmp_lowpan_test.rs
      • boards/imix/src/test/linear_log_test.rs
      • boards/imix/src/test/log_test.rs
      • boards/imix/src/test/rng_test.rs
      • boards/imix/src/test/udp_lowpan_test.rs
        • start()
        • start_rx()
        • start_with_app()
        • start_dual_rx()
      • boards/imix/src/test/virtual_uart_rx_test.rs
      • boards/imix/src/test/multi_alarm_test.rs
  • Microbit-specific Tests

    • examples/accel-leds
    • examples/music
    • examples/tests/ble/ble_advertise
  • Miscellaneous

    • Scheduler Tests
      • whileone + blink
      • restart whileone using process console
      • stop and start whileone
      • whileone + blink + hello_loop using MLFQ scheduler

Metadata

Metadata

Assignees

Labels

release-blockerIssue or PR that must be resolved before the next release

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions