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.

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

Missing tracelog/error line #6114

Closed
trickreich opened this issue May 2, 2018 · 12 comments · Fixed by #6117
Closed

Missing tracelog/error line #6114

trickreich opened this issue May 2, 2018 · 12 comments · Fixed by #6117

Comments

@trickreich
Copy link
Contributor

What 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:
image

Result on CircleCI:
image

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
@SimenB
Copy link
Member

SimenB commented May 2, 2018

I ran this on my mac, and it works.

image

What's your PWD locally?

@trickreich
Copy link
Contributor Author

Ok, looks like it has something todo with the length of the path?
/home/patrick/Sandbox/sulu2/vendor/sulu/sulu

@trickreich
Copy link
Contributor Author

When I'm moving it to /home/patrick/Sandbox/sulu it works.

@SimenB
Copy link
Member

SimenB commented May 2, 2018

I wonder if we do something clever with vendor

@trickreich
Copy link
Contributor Author

Hmm.. ok.. what does this means for us?
Can we change this somewhere?
This naming comes from composer...

@SimenB
Copy link
Member

SimenB commented May 2, 2018

@cpojer should we stop stripping out vendor from the trace?

@cpojer
Copy link
Member

cpojer commented May 2, 2018

Oh yeah, for sure. The only reason we had that was because previously jasmine was in a vendor folder.

@SimenB
Copy link
Member

SimenB commented May 2, 2018

I guess it's a remnant from before #3147, so it should be completely safe to remove now.

EDIT: commented at the same time, cool :D

@trickreich
Copy link
Contributor Author

So we can/should make a PR?

@SimenB
Copy link
Member

SimenB commented May 2, 2018

PR very much welcome! 🙂

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants