intel / intel/gprofiler

tests: nodejs: flaky failure in attach-maps

Open
#584 1 comment 0 reactions 0 assignees View on GitHub
runtime/nodejs
Dominant language
Python
Stars
826
Forks
79
PR merge metrics
No merged PRs in 30d

Description

https://github.com/Granulate/gprofiler/actions/runs/3409188507/jobs/5670935985

```
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.6.15/x64/lib/python3.6/site-packages/granulate_utils/linux/ns.py", line 248, in _switch_and_run
ret = callback()
File "/home/runner/work/gprofiler/gprofiler/gprofiler/metadata/versions.py", line 27, in _run_get_version
return run_process([exe_path, version_arg], stop_event=stop_event, timeout=get_version_timeout)
File "/home/runner/work/gprofiler/gprofiler/gprofiler/utils/__init__.py", line 278, in run_process
raise reraise_exc
gprofiler.exceptions.CalledProcessTimeoutError: Timed out after 3 seconds
Command '['/proc/1/exe', '--version']' died with .
stdout: b''
stderr: b''
```

Do we run the app with limits?

Contributor guide

Open the contributing guide

Research direction

Start with the linked GitHub Actions run and the traceback locations in gprofiler/metadata/versions.py and gprofiler/utils/__init__.py. Investigate the attach-maps failure, including whether the app runs with limits and why /proc/1/exe --version receives SIGKILL after the three-second timeout. Done means the resource-limit cause is established and the flaky test has a defined resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, python
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.