-
Notifications
You must be signed in to change notification settings - Fork 9
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
TMT enablement #83
base: master
Are you sure you want to change the base?
TMT enablement #83
Conversation
plans/smoke.fmf
Outdated
@@ -0,0 +1,9 @@ | |||
summary: Run smoke test | |||
discover: |
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.
I believe discover
steps does not need to be here. You are running a script in execute
a script, thus discovered tests will be ignored I believe
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.
@psss right?
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 your review! Solved
/packit test |
96f2376
to
65fa2ad
Compare
/packit test |
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.
Looks good to me.
If you set the unit test
However it still fails on other deps:
Adding required python module into the plan will fix this:
|
Yes, I know but in that case the Packit will not test installed source but instead it will test always the source code. I want to create new plan which will be ignored by Packit and that will work for the local run. I just didn't had time to finish that yet. Thanks a lot for the prepare info. You saved my time in debugging that ;). |
UPDATED:
|
9cbd640
to
c7419f7
Compare
@psss What do you think, any space for improvement of my new configuration? |
@thrix any idea about when my TMT configuration may work on cruncher? |
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.
I am sorry, but I don't understand it at all.
Looks good. Perhaps, if you would prefer to have both tests defined in a single file, you can do it like this: summary: Run unit tests
description: Run all unit tests for the Simpleline project.
contact: Jiri Konecny <jkonecny@redhat.com>
duration: 10m
/source:
summary+: ' (source)'
test: ./tests/units/run_test.sh
path: /
tag: local
/system:
summary+: ' (system installed)'
test: ./units/run_test.sh
path: /tests
tag: system The extended summary is, of course, just an optional enhancement. |
Wanted to make last week, did not work out :/ .. so this week, I plan to work on it from tomorrow |
c7419f7
to
3479e5c
Compare
UPDATED:
|
jenkins, test this please |
/packit build |
1 similar comment
/packit build |
Ah F33 has branched, I am fixing fedora-32 now. |
/packit test |
1 similar comment
/packit test |
Sorry I messed up, deploying another fix |
/packit test |
fixed :) |
/packit test |
/packit build |
/packit test |
/packit build |
3479e5c
to
77dee87
Compare
/packit build |
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.
Looks good to me now. Thank you!
Seems this is still blocked by Cruncher:
I hope it will be fixed soon :(. |
@jkonecny12 we are almost there, but we got blocked on getting CentOS into AWS :/ Sorry for the delay |
Do we really need to have all these files all over the repository? Isn't there some way to have them contained in .fmf, or tests/tmt, or such? Also, it makes no sense to me that we're enabling TMT but all related filesystem bits are called FMF. |
The
But storing test code & metadata under
The Hope this helps. |
Looking forward to that! Thanks for the update. |
And that would happen in some configuration file? (Just asking to understand.)
Well, both yes and no... I mean, from the testing point of view, certainly yes. But if I'm a wannabe contributor, open the repository and see the file listing, I see mostly stuff not really related to developing the thing. With some .hidden directories I can at least tell I can ignore them. Hope that explains why I'm asking.
Thank you, it does! |
Hi @VladimirSlavik , please ask me directly. I think I'm able to answer most of your questions and it's much easier to discuss this on BJ/IRC than GH. ;) |
plans/local/main.fmf
Outdated
discover+: | ||
filter: tag:local | ||
prepare: | ||
- name: Install missing dependencies |
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.
This syntax is invalid. I copied that in my own playground, and filed a wrong bug as I was misled by the failure output.
prepare:
is a dict, not a list. See the documentation
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 a lot for your insight. Interesting, I'm pretty sure that worked locally :D
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.
At the end this syntax seems to be supported, see:
https://github.com/psss/tmt/blob/master/plans/unit.fmf#L9
Seems that any stage could be specified like this to be able specify multiple different steps. However, it's not really required here.
Unfortunately, I can't find any sign about this in the documentation. Am I missing something @psss?
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.
Yes, steps support multiple definitions. This is documented in the multiple configs section and included in the examples as well. Were would you suggest to add an additional mention about this?
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.
@psss
Ohh, thanks a lot for the pointers. I totally missed the multiple configs
section. I guess the problem is that it's just in the Examples
section and not mentioned in the Specification part
. So maybe, it would be nice to add this to Metadata Specification
section too with explanation that both variants are valid.
FTR, I played around with that a bit, and https://github.com/martinpitt/python-simpleline/pull/1 now runs the tests correctly (except for a pylint version issue on older Fedoras, but that's not TMT's fault). Still requires some hacks, but these are said to go away with the TMT migration. So indeed let's wait with this for a bit until that happened. Until then, we have unit tests on github. |
77dee87
to
07bdd4f
Compare
UPDATED:
|
/packit build |
07bdd4f
to
12eeab5
Compare
/packit build |
Removing my old nack -- LGTM if it works, thanks!
This configuration will work only for PR testing or gating.
PR-testing and Gating have to test unit-tests based on the installed package, however, when we are running these tests in local then we want to start the tests on source and not the installed package. Create two plans to solve this issue.
12eeab5
to
c8ef888
Compare
Enable TMT for Simpleline unit tests and smoke test.
This will be used by Packit and could be run locally.
TODO: