-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2022q1 release #842
2022q1 release #842
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
modm-devices also needs to be fixed, the CI is failing since a new STM32U5 was released and it's missing the memory model. |
9c34fb1
to
ff2fcb1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing the release!
But…… I have opinions…
I guess we'll do it next time? |
No STM32U5 targets are enabled in modm yet. Before we do that I'd say it's not that critical for the release and we can move it. |
Christopher should be added as maintainer to the docs too: |
Done |
6217573
to
175f915
Compare
Unittests Nucleo F103 AFailed 18 of 2645 tests
Unittests Nucleo F103 BPassed 2060 tests
Unittests Nucleo L432Passed 4876 tests
Unittests Nucleo F411Failed 11 of 6026 tests
Unittests Nucleo L552Passed 4876 tests
Unittests Nucleo F091Assertion 'nvic.undef' @ 0xFFFFFFF3 (4294967283) failed!␊ Abandoning...␊
|
Only the gpio sampler/test and spi bitbang unittests are failing, same as last release (#797 (comment)). |
@salkinium Could you check the unittests on MacOS? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approval from me ✅
d1ae191
to
ec18352
Compare
Thanks for doing the release! Nice to know the modm bus factor is not 1 anymore ;-P https://doc.modm.io needs to get the 2022q1 release, I guess by copying a folder somewhere? |
We should automate that for the next release with an on release github action. |
Yes, already done (5 minutes ago). Thanks for reminding.
Won't work because the CI has very limited access to the server that hosts https://docs.modm.io (for security reasons). |
I don't see what the difference is to uploading the
The built file is uploaded via a https request and something on the server extracts the archive to the right place. A simplistic solution for doing it for the release docs could be using a different file name that contains the release name (e.g. |
Actually, we have a problem with https://docs.modm.io hosting: The filesystem (ext4) dedicated for docs.modm.io has run out of inodes: $ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
[...]
/dev/vdaX 2692224 2692224 0 100% /mnt/docs-modm-io-fs because a single release adds nearly 1 million inodes/files: $ find 2021q4/ | wc -l
788108 |
Let's reformat the entire disk to add a new filesystem for every release!1!! |
Done. 7882287 inodes are left for future releases 😆 |
It's quarterly release time again! 2022-04-01 is the date.
lv_indev.c:413:21: error: format '%d' expects argument of type 'int', but argument 6 has type 'uint32_t' {aka 'long unsigned int'} [-Werror=format=]
I2S driver #769changed mcp2515 driver to use nonblocking spi #817modm::PeriodicTimer
constructor inmodm::BitBangEncoderOutput
Unittests on WindowsUnittests on Arduino UnoUnittests on AVR Mega 2560 Pronext time™