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.

Sign up for GitHub

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

Jump to bottom

[FTR] Unable to connect to debugger #95248

Closed
tylersmalley opened this issue Mar 23, 2021 · 1 comment · Fixed by #95344
Closed

[FTR] Unable to connect to debugger #95248

tylersmalley opened this issue Mar 23, 2021 · 1 comment · Fixed by #95344
Assignees
@mistic
Labels
bug Fixes for quality problems that affect the customer experience Feature:Functional Testing Team:Operations Team label for Operations Team

Comments

@tylersmalley
Copy link
Contributor

After daa0f22, you're no longer able to start the functional test runner with a debug breakpoint.

After starting the FTR with node --inspect-brk scripts/functional_test_runner you will see Starting inspector on 127.0.0.1:9229 failed: address already in use and the debugger will not work as expected.
@tylersmalley tylersmalley added bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team Feature:Functional Testing labels Mar 23, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@mistic mistic mentioned this issue Mar 24, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mistic mistic

Labels
bug Fixes for quality problems that affect the customer experience Feature:Functional Testing Team:Operations Team label for Operations Team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(NA): support inspect flags on ensure_node_preserve_symlinks script mistic/kibana
3 participants
@tylersmalley @mistic @elasticmachine