ron litzenberger
ron litzenberger
I have removed the JS->go tests from the runner until this is resolved. To create error run: ` node extract-js2.go.js`
With the recent changes, warmup may not be working as expected. Need to verify.
removed this feature for now.
It wasn't working and figured it was a lower priority over adding tests.
ok yep sounds good.
Yes, will write this test now.
Added js -> go and go -> js. Here are the results running locally: js -> go ``` ────────────────────┬────────────────────┬──────────────────────────────────────────────────┬────────────────────┬─────────────────────┐ │ Test │ Warmup │ Description │ File Set │ Duration...
Clinic reports for js -> go https://upload.clinicjs.org/public/238842ad20f8542b91743e377f21ab9f455dcddfea3bc0702830c401da302bbf/34523.clinic-doctor.html https://upload.clinicjs.org/public/d0491b68df5b070fa226600ac4ce0389d04f35ab4e7f2aa0c718d5ae615101e4/34583.clinic-flame.html https://upload.clinicjs.org/public/ad48c42cc98c35249690f2a8bb8b7a05880de6e8b3f781a5c720c42e06d0489c/34730.clinic-bubbleprof.html
@Elexy I think the js-ipfs tests in the repo are fine, he just wants to pull another repo that will need to be synced by the runner. @vasco-santos did I...
Added a few go benchmarks but had to remove them due to https://github.com/ipfs/benchmarks/issues/241