Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] measure code is running under incorrect Node.js configuration

See original GitHub issue

I’m getting this message when running yarn reassure:

console.error ❌ Reassure: measure code is running under incorrect Node.js configuration. Performance test code should be run in Jest with certain Node.js flags to increase measurements stability. Make sure you use the Reassure CLI and run it using “reassure” command.

Same with npx reassure or yarn node --expose_gc $(yarn bin reassure).

reassure: v0.4.1 node: v14.17.6 yarn: v1.22.19 jest: v26.6.3 MBP M1 macOS: v12.4

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

sreggcommented, Sep 21, 2022

Removing jest-expo and setting preset: react-native worked 🎉 The test was very slow though (200s)

simonreggiani@Simons-MacBook-Pro-2 mobile-app % yarn reassure
yarn run v1.22.19
$ /Users/simonreggiani/dev/mobile-app/node_modules/.bin/reassure

❇️  Running current performance tests:

 PASS  test/performance/search-filters-screen.perf-test.tsx (202.485 s)
  Search Filters Screen Performance
    ✓ Select 3br (18517 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        203.02 s
Ran all test suites.

✅  Written current performance measurements to .reassure/current.perf
🔗 /Users/simonreggiani/dev/mobile-app/.reassure/current.perf

Baseline performance file does not exist, run 'reassure --baseline' on your baseline code branch to create it.

✨  Done in 204.20s.
thymikeecommented, Sep 21, 2022

What if you replaced jest-expo preset with react-native? Would be great if you tried running our examples and see if there’s anything in your environment that gets in the way

Read more comments on GitHub >

github_iconTop Results From Across the Web

Errors | Node.js v19.3.0 Documentation
Error objects capture a "stack trace" detailing the point in the code at which the Error was instantiated, and may provide a text...
Read more >
Zlib error when attempting to run npm install or yarn
So here's my suggestion: uninstall Node 14.18.x and try using Node 14.17.x instead. As a side note, you may find it useful to...
Read more >
15 Common Error Codes in Node.js and How to Fix Them
1. ECONNRESET ... If this exception occurs when making a request to another server, you should catch it and decide how to handle...
Read more >
6 reasons your Node.js apps are failing - IBM Developer
Excessive memory usage, which may result in an out-of-memory error; Unresponsive application, possibly looping or hanging; Poor performance; Crash or abort in ......
Read more >
A Comprehensive Guide To Error Handling In Node.js
Errors happen in every application. Devs have to decide: do you write code to handle the error? Suppress it? Notify the user?
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found