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.

Sign up for GitHub

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

Jump to bottom

Investigate and optimize running filled tests #1020

Open
SamWilsn opened this issue Oct 5, 2024 · 1 comment
Open

Investigate and optimize running filled tests #1020

SamWilsn opened this issue Oct 5, 2024 · 1 comment
Labels
A-tool Area: tooling C-bug Category: this is a bug, deviation, or other problem. E-hard Experience: difficult, probably not for the faint of heart P-high
Milestone
Post-Prague Re-fa...

Comments

@SamWilsn
Copy link
Contributor

SamWilsn commented Oct 5, 2024

With the t8n daemon, we can fill tests in a matter of minutes. Running the tests, for some reason, takes several hours.

That should not be the case.
@SamWilsn SamWilsn added A-tool Area: tooling C-bug Category: this is a bug, deviation, or other problem. E-hard Experience: difficult, probably not for the faint of heart labels Oct 5, 2024
@SamWilsn SamWilsn added this to the Post-Prague Re-factoring milestone Feb 13, 2025
@SamWilsn
Copy link
Contributor Author

  1. Support t8n's consume mode #1025
  2. Remove most of the code from our tests directory
  3. Loop over all the files in the tests directory, and call our t8n consume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-tool Area: tooling C-bug Category: this is a bug, deviation, or other problem. E-hard Experience: difficult, probably not for the faint of heart P-high
Projects
None yet
Milestone
Post-Prague Re-factoring
Development

No branches or pull requests
2 participants
@petertdavies @SamWilsn