-
Notifications
You must be signed in to change notification settings - Fork 2.1k
buildsystem: Remove buildtest
Goal & Fix info-buildsizes-diff
#21359
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
Conversation
The example for Furthermore, Also, it will show RIOT/makefiles/info-global.inc.mk Lines 129 to 130 in fb7acf5
The only place where RIOT/doc/doxygen/src/getting-started.md Lines 318 to 331 in fb7acf5
But Is that used for something else? Or is it even useful to begin with? RIOT/.github/workflows/tools-test.yml Lines 41 to 42 in fb7acf5
|
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.
Thx for cleaning this up!
@@ -9,7 +9,6 @@ This example should foremost give you an overview how to use the Makefile system | |||
* First you must give your application a name, which is commonly the same as the name of the directory it resides in. | |||
Then you can define a default BOARD for which the application was written. | |||
By using e.g. `make BOARD=msba2` you can override the default board. |
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.
Ah, the good old MSB-A2 still is the "default" board in our doc :D
And 14.2 GiB of that were the |
It turns out that I changed the behavior of Now
|
3d1ef72
to
c5450fc
Compare
c5450fc
to
1670077
Compare
buildtest
Goalbuildtest
Goal & Fix info-buildsizes-diff
Okay so the The documentation in RIOT/doc/doxygen/src/getting-started.md Lines 318 to 331 in fb7acf5
docker pull riot/riotdocker does not work anymore.
The |
I removed this from the merge queue for now, so someone can take a second look at it again, now that two more scripts are removed and the documentation is updated. |
3e44741
to
0d15ac7
Compare
The Without |
9563487
to
7543be5
Compare
@crasbe with the riotdocker CI still using |
I thought I researched this more thoroughly, but apparently that got missed. Sorry for the mess that it caused. To answer the question: yes, that should be a valid substitution. However one thing that still has to be checked it how the Github workflow evaluates whether the run was successful or not. As far as I can tell, the Python script always returns success? |
Contribution description
The
buildtests
goal was an early version used for compiling all boards.There is still a reference in the documentation that has to be changed, but I'm not familiar with
make generate-makefiles.ci
, so input in this regard is very welcome.RIOT/doc/doxygen/src/advanced-build-system-tricks.md
Lines 178 to 196 in fb7acf5
Likewise in
dist/tools/compile_test/compile_test.py
:RIOT/dist/tools/compile_test/compile_test.py
Lines 127 to 130 in fb7acf5
Testing procedure
Make sure your favorite board and favorite application still build.
Make sure that no references to
buildtest
orbuildtests
remain, for example withgrep -Rnw . -e buildtest
.Issues/PRs references
Fixes #9742.
Alternative approach for #21355.