improve maitake timer wheel #1336
ci.yml
on: pull_request
changed_paths
7s
cargo check (host)
3m 38s
rustfmt
25s
clippy
2m 55s
cargo test (host)
4m 47s
build boot image (x86_64)
3m 15s
cargo test (cross x64)
4m 37s
docs
2m 9s
Loom tests (cordyceps)
1m 42s
Miri tests (codyceps)
1m 57s
Tests (maitake, no-default-features)
1m 53s
Loom tests (maitake)
50s
Loom tests (mycelium-util)
58s
Annotations
12 errors and 8 warnings
Loom tests (maitake)
Process completed with exit code 101.
|
Tests (maitake, no-default-features)
Process completed with exit code 101.
|
docs:
maitake/src/time/clock.rs#L13
error: public documentation for `Clock` links to private item `Ticks`
--> maitake/src/time/clock.rs:13:20
|
13 | /// timestamp in [`Ticks`], and a [`Duration`] that defines the amount of time
| ^^^^^ this item is private
|
= note: this link will resolve properly if you pass `--document-private-items`
= note: `-D rustdoc::private-intra-doc-links` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(rustdoc::private_intra_doc_links)]`
|
docs:
maitake/src/time/clock.rs#L127
error: unresolved link to `named`
--> maitake/src/time/clock.rs:127:70
|
127 | /// Returns this `Clock`'s name, if it was given one using the [`named`]
| ^^^^^ no item named `named` in scope
|
= help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
= note: `-D rustdoc::broken-intra-doc-links` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(rustdoc::broken_intra_doc_links)]`
|
docs:
maitake/src/time/timer.rs#L65
error: unresolved link to `Timer::advance`
--> maitake/src/time/timer.rs:65:58
|
65 | /// must be driven by a *time source*, which calls the [`Timer::advance`] method
| ^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `advance`
|
docs:
maitake/src/time/timer.rs#L66
error: unresolved link to `Timer::force_advance`
--> maitake/src/time/timer.rs:66:47
|
66 | /// and/or the [`Timer::pend_duration`] and [`Timer::force_advance`] methods.
| ^^^^^^^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `force_advance`
|
docs:
maitake/src/time/timer.rs#L86
error: unresolved link to `Timer::advance`
--> maitake/src/time/timer.rs:86:7
|
86 | /// [`Timer::advance`] methods.
| ^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `advance`
|
docs:
maitake/src/time/timer.rs#L88
error: unresolved link to `Timer::advance`
--> maitake/src/time/timer.rs:88:7
|
88 | /// [`Timer::advance`] will attempt to optimistically acquire a spinlock, and
| ^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `advance`
|
docs:
maitake/src/time/timer.rs#L99
error: unresolved link to `Timer::force_advance_ticks`
--> maitake/src/time/timer.rs:99:7
|
99 | /// [`Timer::force_advance_ticks`] method periodically outside of the interrupt
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `force_advance_ticks`
|
docs:
maitake/src/time/timer.rs#L115
error: unresolved link to `Timer::advance_ticks`
--> maitake/src/time/timer.rs:115:7
|
115 | /// [`Timer::advance_ticks`]`(1)` or [`Timer::pend_ticks`]`(1)` in the interrupt
| ^^^^^^^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `advance_ticks`
|
docs:
maitake/src/time/timer.rs#L134
error: unresolved link to `Timer::advance`
--> maitake/src/time/timer.rs:134:7
|
134 | /// [`Timer::advance`] method should generally be used to drive the timer. Prior
| ^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `advance`
|
docs:
maitake/src/time/timer.rs#L135
error: unresolved link to `Timer::advance`
--> maitake/src/time/timer.rs:135:18
|
135 | /// to calling [`Timer::advance`], the time source is read to determine the
| ^^^^^^^^^^^^^^ the struct `Timer` has no field or associated item named `advance`
|
Loom tests (maitake)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: extractions/setup-just@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Loom tests (mycelium-util)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: extractions/setup-just@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Loom tests (cordyceps)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: extractions/setup-just@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Miri tests (codyceps)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: extractions/setup-just@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
docs
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: extractions/setup-just@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
clippy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: extractions/setup-just@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
cargo check (host):
trace/src/embedded_graphics.rs#L132
warning: unused variable: `actual_point`
--> trace/src/embedded_graphics.rs:132:17
|
132 | Err(actual_point) => unsafe {
| ^^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_actual_point`
|
= note: `#[warn(unused_variables)]` on by default
|
cargo test (host)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: extractions/setup-just@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|