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

kola: Add a filter to run tests based on offering #158

Merged
merged 2 commits into from
Jan 18, 2021

Conversation

sayanchowdhury
Copy link
Member

@sayanchowdhury sayanchowdhury commented Jan 5, 2021

kola: Add a filter to run tests based on offering

With the introduction of the Pro offering, it is not possible to
test Pro specific features or test just for Pro without them runing
on the basic offering as well. This changes introduces a new flag
that helps building a clear distinction between Pro and the nornal
offering.

The excludeOffering maybe does not make sense now with two offering
but kept it for future feasibility.

Signed-off-by: Sayan Chowdhury [email protected]

How to use

./build kola
./bin/kola run --offering=pro

Testing done

Not done yet.

Copy link
Member

@pothos pothos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested with bin/kola list --filter --offering pro --platform qemu after adding some annotations to tests

@sayanchowdhury sayanchowdhury marked this pull request as ready for review January 6, 2021 11:08
@sayanchowdhury
Copy link
Member Author

I've updated tests with the Offering param so that it is easier and cleaner in jenkins to just pass the parameter basic or pro.

@sayanchowdhury sayanchowdhury requested review from pothos and a team January 7, 2021 12:34
@@ -72,7 +72,8 @@ func init() {
"Useradd": TestUseradd,
"MachineID": TestMachineID,
},
Distros: []string{"cl"},
Distros: []string{"cl"},
Offerings: []string{"basic", "pro"},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit confused here, do we really need to specify this field for each and every test? We don't do this for Architectures or Channels... Why do we need to do it for Offerings?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated Offerings similar to how Architectures and Channels are. I was thinking for a future case, where we have more offers, and miscalculated. Sorry for the confusion.

@sayanchowdhury sayanchowdhury force-pushed the sayan/add-kola-filter-offering-based branch 2 times, most recently from d4a6f97 to 8d0bc58 Compare January 8, 2021 04:29
Copy link
Contributor

@margamanterola margamanterola left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

With the introduction of the Pro offering, it is not possible to
test Pro specific features or test just for Pro without them runing
on the basic offering as well. This changes introduces a new flag
that helps building a clear distinction between Pro and the nornal
offering.

Signed-off-by: Sayan Chowdhury <[email protected]>
@sayanchowdhury sayanchowdhury force-pushed the sayan/add-kola-filter-offering-based branch from 8d0bc58 to a87b7cc Compare January 18, 2021 15:42
@sayanchowdhury sayanchowdhury merged commit b140df5 into flatcar-master Jan 18, 2021
@sayanchowdhury sayanchowdhury deleted the sayan/add-kola-filter-offering-based branch January 18, 2021 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants