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

[Tracking issue] Infrastructure for Stage 2 #159

Closed
3 tasks
aborg-dev opened this issue Dec 11, 2023 · 1 comment
Closed
3 tasks

[Tracking issue] Infrastructure for Stage 2 #159

aborg-dev opened this issue Dec 11, 2023 · 1 comment
Labels
C-housekeeping Category: Refactoring, cleanups, code quality

Comments

@aborg-dev
Copy link

aborg-dev commented Dec 11, 2023

This is a tracking issue for all infrastructure work for Stage 2.

As our test and benchmarking suite grows, we should invest more time to make it convenient to work with them.
In an ideal world, after every change we would get a clear report of the effects on the performance and correctness of the tests - we could even generate such a report as a part of a PR request (e.g. using a CI bot).
In the same way, we need a fast local tooling that can present such a report.

Tasks

Preview Give feedback
  1. 2 of 9
    MCJOHN974
  2. 0 of 4
    mooori
  3. enhancement good first issue
@aborg-dev aborg-dev added the C-housekeeping Category: Refactoring, cleanups, code quality label Dec 11, 2023
@aborg-dev aborg-dev added this to the ZK WASM: Stage 2 milestone Dec 11, 2023
@aborg-dev aborg-dev changed the title Introduce infrastructure for Stage 2 Prepare infrastructure for Stage 2 Dec 11, 2023
@aborg-dev aborg-dev changed the title Prepare infrastructure for Stage 2 [Tracking issue] Infrastructure for Stage 2 Jan 2, 2024
@aborg-dev
Copy link
Author

I'm closing this in favor of more fine-grained tracking issues about testing and benchmarking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-housekeeping Category: Refactoring, cleanups, code quality
Projects
None yet
Development

No branches or pull requests

1 participant