[DO NOT REVIEW] checking if perf testing is broken #50812
Conversation
|
@typescript-bot perf test this faster |
|
Heya @jakebailey, I've started to run the abridged perf test suite on this PR at ce7854e. You can monitor the build here. |
|
@typescript-bot perf test this faster |
|
Heya @jakebailey, I've started to run the abridged perf test suite on this PR at 89658ee. You can monitor the build here. |
jakebailey
force-pushed
the
empty-commit
branch
from
89658ee
to
e2ad372
Compare
|
@typescript-bot perf test this faster |
|
Heya @jakebailey, I've started to run the abridged perf test suite on this PR at e2ad372. You can monitor the build here. |
|
Do ignore the contents of this PR; I'm trying silly things includeing rolling main back to the last state I knew the benchmarks ran on. @weswigham @gabritto are trying other things too, but of course we all can't run perf benchmarks at the same time (and also the release branch was just merged into so now that's running too) |
|
AFAIK the issue is that the folder isn't clean, and I broke the folder once in my module testing PR, and that left dirty files that made other tests bad. Fix for now is to clean the PR, but that may slow down perf testing because of reclones of the repo, depending. |
No description provided.