No INFO/DEBUG log if Python ValidatesRunner test timeout
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Python service test (ValidatesRunner test and Integration test with service runner) enabled multiprocess execution in Postcommit through Nose. When TimedOutException happens, only stack trace are printed out which contains very little information about job info. Printing whatever logs until timeout happens, which is captured by Nose, will make debugging on service more easier.
This is a issue on Nose framework side and there is a link to track: https://github.com/nose-devs/nose/issues/1044
Imported from Jira [BEAM-1890](https://issues.apache.org/jira/browse/BEAM-1890). Original Jira may contain additional context.
Reported by: markflyhigh.
Contributor guide
Research direction
Start with the Python ValidatesRunner and integration tests that use the service runner, and review how Nose runs their multiprocess Postcommit execution. Check nose-devs/nose#1044 for the timeout behavior; done means INFO/DEBUG logs captured before TimedOutException are printed with enough job context to debug the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100