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

Issue 1993 + Issue 2057 (Benchmarks provisioning) #2061

Merged
merged 9 commits into from
Sep 17, 2024

Conversation

itsmesamster
Copy link
Collaborator

No description provided.

@itsmesamster itsmesamster reopened this Jul 24, 2024
@itsmesamster itsmesamster changed the title Commit working code Issue 1993 + Issue 2057 (Benchmarks provisioning) Jul 26, 2024
@itsmesamster itsmesamster force-pushed the issue_1993 branch 10 times, most recently from d944ab7 to 36d1a51 Compare August 4, 2024 21:02
@itsmesamster itsmesamster force-pushed the issue_1993 branch 6 times, most recently from 8fe2985 to 82af496 Compare August 13, 2024 09:17
@itsmesamster itsmesamster marked this pull request as ready for review August 27, 2024 10:55
@itsmesamster itsmesamster force-pushed the issue_1993 branch 3 times, most recently from 8a5d44d to 2a9d552 Compare September 4, 2024 14:04
@DmitryAstafyev
Copy link
Collaborator

@itsmesamster great job Sameer! Let's also consider new build CLI sys to run benchmarks and let it go

@DmitryAstafyev
Copy link
Collaborator

@AmmarAbouZor in the scope of this PR we would need an additional build CLI command. Right now we have the command cargo chipmunk test [TARGET] (targets: core, shared, binding, wrapper, wasm, client, updater, app, cli). But we would need a custom js test runner to replace this (with ruby):

Shell.sh "#{Paths::JASMINE} spec/build/spec/session.#{spec}.spec.js"

To something like this (with CLI):

cargo chipmunk test bindings --custom=full_path/spec/build/spec/benchmarks.spec.js

Could you please take care of it as soon as you will have some time?

@AmmarAbouZor AmmarAbouZor self-assigned this Sep 9, 2024
@AmmarAbouZor
Copy link
Member

Hi @DmitryAstafyev @itsmesamster
Selecting custom specs is implemented in CLI tool. Now it's possible to specify one or multiple tests as following:

  • cargo chipmunk test wrapper -s spec/build/spec/session.jobs.spec.js: Runs single specification.
  • cargo chipmunk test wrapper -s spec/build/spec/session.jobs.spec.js -s spec/build/spec/session.search.spec.js: Runs multiple specifications.

I've increased the version of the tool and added the change to the CHANGELOG as well.

itsmesamster and others added 9 commits September 13, 2024 14:01
* Users can set custom wrapper tests via CLI arguments.
* Custom specs is prepared to be used with different jobs when needed
* Refactor: Create struct `JobConfigs` to represent jobs state configs
* Fix: Rename `child` to `cmd`.
* Increase tool version and add changes to CHANGELOG
* Add missing build rust core step with linting and testing jobs
  for binding, wrapper and app targets
* Improve code comments to clarify the complex logic code in that
  position
@DmitryAstafyev DmitryAstafyev merged commit 0cc3c28 into esrlabs:master Sep 17, 2024
4 checks passed
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