Missing tracelog/error line
See original GitHub issueWhat is the expected behavior? Jest prints out the tracelog, especially points to the correct line number in the code.
Current behavior? In our project there’s no tracelog or line number where the error has happend. We are using CircleCI for CI testing and there the tracelog is visible! We searched for months now, what is wrong with our setup, but now it looks there’s something wrong with our machines?
I hope someone can point me here in the right direction!
Result on my machine:
Result on CircleCI:
Link to the CircleCI PR: https://circleci.com/gh/sulu/sulu/1173?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
Please provide your exact Jest configuration Everything is open source: https://github.com/sulu/sulu/blob/develop/package.json#L65
Tested on different machines:
Linux:
npx: installed 1 in 2.626s
System:
OS: Linux 4.15 Ubuntu 18.04 LTS (Bionic Beaver)
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Binaries:
Node: 8.10.0 - /usr/bin/node
npm: 6.0.0 - /usr/local/bin/npm
npmPackages:
jest: ^22.4.0 => 22.4.3
OSX:
npx: Installierte 1 in 3.31s
System:
OS: macOS High Sierra 10.13.2
CPU: x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
Binaries:
Node: 9.3.0 - /usr/local/bin/node
Yarn: 1.3.2 - /usr/local/bin/yarn
npm: 5.6.0 - /usr/local/bin/npm
npmPackages:
jest: ^22.4.0 => 22.4.3
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (5 by maintainers)
Top GitHub Comments
So we can/should make a PR?
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.