Skip to content

Automate cpu runtime test #14508

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

Merged
merged 4 commits into from
Nov 15, 2022
Merged

Conversation

Furisto
Copy link
Member

@Furisto Furisto commented Nov 8, 2022

Description

Implement an integration test to automate the cpu runtime tests.

Related Issue(s)

Fixes #14221

How to test

  • Run tests

Release Notes

None

Documentation

Werft options:

  • /werft with-local-preview
    If enabled this will build install/preview
  • /werft with-preview
  • /werft with-large-vm
  • /werft with-integration-tests=workspace
    Valid options are all, workspace, webapp, ide

@Furisto Furisto added the team: workspace Issue belongs to the Workspace team label Nov 8, 2022
@Furisto Furisto requested a review from a team November 8, 2022 10:44
@Furisto Furisto self-assigned this Nov 8, 2022
@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-furisto-test-integration-test-for-14221.10 because the annotations in the pull request description changed
(with .werft/ from main)

@roboquat roboquat added the size/L label Nov 8, 2022
@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-furisto-test-integration-test-for-14221.11 because the annotations in the pull request description changed
(with .werft/ from main)

@Furisto Furisto force-pushed the furisto/test-integration-test-for-14221 branch from 940c3bc to 28f62a2 Compare November 10, 2022 10:42
)

func TestCpuBurst(t *testing.T) {
f := features.New("cpulimiting").WithLabel("component", "ws-manager").Assess("check cpu limiting", func(_ context.Context, t *testing.T, cfg *envconf.Config) context.Context {
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we have to add a check if there is a configuration to enable CPU limit and if there isn't we should skip the test.

@Furisto Furisto force-pushed the furisto/test-integration-test-for-14221 branch 2 times, most recently from 543951c to 78735cd Compare November 14, 2022 14:29
@Furisto
Copy link
Member Author

Furisto commented Nov 14, 2022

@utam0k PTAL


func TestCpuBurst(t *testing.T) {
f := features.New("cpulimiting").WithLabel("component", "ws-manager").Assess("check cpu limiting", func(_ context.Context, t *testing.T, cfg *envconf.Config) context.Context {
ctx, cancel := context.WithTimeout(context.Background(), 5*time.Minute)
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this time enough to wait for burst?

Copy link
Member Author

Choose a reason for hiding this comment

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

It should be enough, but I increased it just in case.

f := features.New("cpulimiting").WithLabel("component", "ws-manager").Assess("check cpu limiting", func(_ context.Context, t *testing.T, cfg *envconf.Config) context.Context {
ctx, cancel := context.WithTimeout(context.Background(), 5*time.Minute)
defer cancel()

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
t.Parallel()

@Furisto Furisto force-pushed the furisto/test-integration-test-for-14221 branch from 78735cd to ab42b2d Compare November 15, 2022 11:26
Copy link
Contributor

@utam0k utam0k left a comment

Choose a reason for hiding this comment

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

/hold
until test will be passed

@Furisto
Copy link
Member Author

Furisto commented Nov 15, 2022

/unhold

@roboquat roboquat merged commit b413431 into main Nov 15, 2022
@roboquat roboquat deleted the furisto/test-integration-test-for-14221 branch November 15, 2022 13:10
@roboquat roboquat added deployed: workspace Workspace team change is running in production deployed Change is completely running in production labels Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: workspace Workspace team change is running in production deployed Change is completely running in production release-note-none size/L team: workspace Issue belongs to the Workspace team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[test] integration test for cpu bursting
4 participants