Skip to content
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

tuxml-kci script: make it work! #37

Open
FAMILIAR-project opened this issue Jan 21, 2021 · 0 comments
Open

tuxml-kci script: make it work! #37

FAMILIAR-project opened this issue Jan 21, 2021 · 0 comments
Assignees

Comments

@FAMILIAR-project
Copy link
Collaborator

FAMILIAR-project commented Jan 21, 2021

That is, calling the script for the three parameters (gcc version, kernel version, ways of picking a configuration) should give something.
Docker should be used to host the necessary tools (compilers as well as kci tool suite).

I'm expecting a functional demonstration ASAP. "Functional" means that some results are produced.
The dev is actually in another repo: https://github.com/TuxML/tuxml-kci

Then, to further test the script, we should compare it with tuxml (without kci).
Conceptually, tuxml and tuxml-kci actually implement the same functionnaly ksize (c, kv, cc) = bz (see above)
So an experiment for testing is to check that for the same configuration, kernel version, and compiler version, we have the same build status and same binary size.
This experiment should be done on several configurations and kernel versions that already exist in the database (data made with tuxml).
A script can automate the testing by simply calling tuxml-kci, gathering the results, compare and conclude.

@FAMILIAR-project FAMILIAR-project created this issue from a note in TuxML roadmap 2021 (tuxml-kci script) Jan 21, 2021
@Nusky173 Nusky173 self-assigned this Jan 27, 2021
@ThomasTSY ThomasTSY self-assigned this Jan 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
TuxML roadmap 2021
tuxml-kci script
Development

No branches or pull requests

3 participants