2021q4 release #797
Merged
2021q4 release #797
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LVGL v8.1.0 issues: FreeRTOS+TCP 202112.00 issues: |
|
@rleh if you have time until new year, could you test if the updated FreeRTOS+TCP is still working in hardware? |
salkinium
force-pushed
the
release/2021q4
branch
from
0da16a0 to
5c42ba7
Compare
|
@salkinium We should include #772 in the release. It fixes broken DMA data for a lot of devices. |
|
I'll merge it tomorrow, so you're not stressed today. |
Compiles with 5ea28f9 and work on my Nucleo-F429ZI 👍🏽 I also opened a PR upstream (FreeRTOS/FreeRTOS-Plus-TCP#403), then hopefully we can remove the fix on our config file before 2022q1 release. |
Do you need help with that? |
|
Yes, please, also if you could fix LVGL, I'm not motivated to do it. That would probably require applying a patch inside the submodule as done with FreeRTOS for example. |
|
In general we should not apply the same flags for third-party code that we apply for modm code. The |
As a quick workaround I modified the auto updater in modm-ext/lvgl to apply a patch to fix the errors. It's on a feature branch for now and I opened a PR: Locally it compiles for me. |
|
I can't test lvgl since I have no boards with a display with me. |
Tested: Works (on STM32F469 DISCO board) ✅
|
Hardware TestsNucleo-F103_A
Nucleo-F103_B
Nucleo-F411
Nucleo-F091
Nucleo-L432
|
|
Ugh, the GPIO Sampler and SPI BitBang stuff is broken itself, rather than the tests. It's probably not relevant. |
salkinium
force-pushed
the
release/2021q4
branch
from
d2ed678 to
3b3d428
Compare
|
Tested TinyUSB in hardware, works fine… I'm going to merge this tomorrow and then do the release. |
salkinium
force-pushed
the
release/2021q4
branch
from
3b3d428 to
b53a7ed
Compare
salkinium
force-pushed
the
release/2021q4
branch
from
b53a7ed to
9bf7d20
Compare
|
@rleh something is broken for the doxygen API docs https://docs.modm.io/develop/api/stm32f469zit6/ |
The Can be reproduced with the test ( $ python3 tools/scripts/docs_modm_io_generator.py -c -j8 -d -t2
[...]
$ tar -tzvf modm-api-docs.tar.gz | grep index
-rw-rw-r-- user/user 7171 2022-01-01 18:25 ./index.html |
|
I am getting segfaults of doxypress on Ubuntu 20.04 with the recent version (1.4.1). |
|
Ah, crap the CI job also segfaults but doesn't show an error… |
Can't reproduce that on my Fedora 35 system with an Doxypress version 1.3.7 and the current version 1.4.1. But the Github Actions log contains a lot of the |
|
v1.4.0 also segfaults on macOS 10.14: But I don't recall this being broken since March 2021, so it's probably something in our config? Edit: Obviously it worked for the Q3 release, so it's not Doxypress itself. |
|
https://github.com/modm-io/modm/runs/4582015012 (triggered by #748) is the first CI job with segmentation faults. |
|
|
|
We could try to re-run the last successful job (https://github.com/modm-io/modm/actions/runs/1596734183), what do you think? Update: In progress https://github.com/modm-io/modm/actions/runs/1596734183 |
|
Sorry, hit the wrong key on the keyboard, Q3 does not work at all for me. Getting an infinite recursion in the docs generator python script ( EDIT: I ran it again and now it works ... |
Got the same behaviour, I think its some bytecode caching somewhere… 🙀 |
|
Exactly the same for me. The commit with the MCP7941X driver makes doxypress crash. |
🙀 🙀 🙀 |
|
At least the issue is just this one driver, so we don't have to do a new release, all other examples seem to generate the documentation just fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's quarterly release time again! 2022-01-01 is the date.
Fix author.py script to detect Co-authored-by correctly.next time™