Fix staging

[moritz-meier]

Last three commits on staging broke armv7a-none-eabi support and serde support did not work.

todo: add serde support on opentaws::alerts::Alerts<Alert>.

edit:
todo: fix code coverage action

edit:
todo: add std support for tests on armv7a-none-eabi
todo: add armv7a-none-eabi test to actions

[dadada]

What do you mean serde support did not work? We used serde support successfully in our WASM demonstrator. I'd be interested in trying to fix this, if you can provide more detail.

[moritz-meier]

I get lots of errors regarding serde when building staging with cargo build --target=armv7a-none-eabi --features=use-serde.

Dont really know why. But this 8b9d556 fixed it.

Did the WASM demo used armv7a-none-eabi?

[dadada]

Did the WASM demo used armv7a-none-eabi?

Yes, it was for a Zynq7000 platform.

[dadada]

Last known good commit: https://github.com/aeronautical-informatics/openTAWS?branch=staging#f711303dd3abe281963523846e7845021a93fc49

[moritz-meier]

Last known good commit: https://github.com/aeronautical-informatics/openTAWS?branch=staging#f711303dd3abe281963523846e7845021a93fc49

Thats currently staging (f711303).

Seems like the problem occurs when resolver = "1" or no resolver is specified in workspace Cargo.toml. When switching to resolver = "2" it builds successfully. (6d67c75)

cargo 1.72.1 (103a7ff2e 2023-08-15)

[moritz-meier]

Lets merge this.

[moritz-meier]

lets go.

[moritz-meier]

@wucke13 Lets merge this.