forked from ariel-os/hophop
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathtest.sh
More file actions
executable file
·55 lines (46 loc) · 1.87 KB
/
Copy pathtest.sh
File metadata and controls
executable file
·55 lines (46 loc) · 1.87 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
#!/bin/sh
# SPDX-FileCopyrightText: Copyright Christian Amsüss <chrysn@fsfe.org>, Silano Systems
# SPDX-License-Identifier: MIT OR Apache-2.0
# Kept in a shell script to be easily portable to no-GitHub CI systems.
#
# This expects the Ariel OS "getting started" setup to be present, and suitable
# caching options to be set.
set -ex
pipx run reuse lint
cargo vet check
RUSTFLAGS="-D warnings" cargo check --workspace
RUSTFLAGS="-D warnings" cargo check --workspace --all-features
cargo clippy --workspace -- --deny clippy::all --deny clippy::pedantic
RUSTDOCFLAGS="-D warnings" cargo doc --workspace --all-features
cargo fmt --check
# hophop can't be built on host architectures
cargo test --workspace --exclude hophop
cargo test --workspace --all-features --exclude hophop
for DIR in ts-103-636-numbers ts-103-636-utils
do
cd "${DIR}"
cargo doc2readme --check
cd ..
done
# Initially those do build tests only; turning clippy and checks on is a good
# next step, but only once these stabilize a little.
# Listing them all so we notice if any fail. (There can be differences in
# build-time issues like "do we have a case for that UART configuration", but
# also laze-time requirements like "this needs an LED", and I'd rather exclude
# them explicitly here then to make sure this matches the docs).
BOARDS="-b nrf9151-dk -b makerdiary-nrf9151-connect-kit -b nordic-thingy-91-x-nrf9151"
cd examples
# We enable IPv6, and current Ariel needs something in there
export CONFIG_NET_IPV6_STATIC_ADDRESS=fe80::1
export CONFIG_NET_IPV6_STATIC_GATEWAY_ADDRESS=::
# FIXME: Going through `run` but not really -- because a plain build fails due to the multiple binaries.
for EX in rx tx rssi ping
do
laze build ${BOARDS} -D LOG=trace -D CARGO_RUNNER=true --multiple-tasks run --bin ${EX}
done
cd ..
cd applications
for APP in embedded-pt bridge-pt
do
laze build -C $APP/ ${BOARDS} -D LOG=trace
done