-
Notifications
You must be signed in to change notification settings - Fork 2
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
check_deadlock is called with context not initialized #2
Comments
This seems like to be a dependency bug of racepro.
The timer got timed out before the context is initialized, therefore the error is thrown. |
does it happen if you increase the deadlock period check ? On 07/06/2011 04:52 PM, chiache wrote:
|
This is not a deterministic bug. I am trying to reproduce it. |
This exception is thrown while replaying the building of php5.
Traceback (most recent call last):
File "/usr/local/bin/racetest", line 151, in
racetest.do_all_tests(args, tests)
File "/usr/local/lib/python2.6/dist-packages/racepro/racetest.py", line 269, in do_all_tests
if not do_one_test(args, t_name, t_exec):
File "/usr/local/lib/python2.6/dist-packages/racepro/racetest.py", line 187, in do_one_test
if not scribewrap.scribe_replay(args):
File "/usr/local/lib/python2.6/dist-packages/racepro/scribewrap.py", line 206, in scribe_replay
wait = not args.max_runtime)
File "/usr/local/lib/python2.6/dist-packages/racepro/scribewrap.py", line 52, in do_check_deadlock
context.check_deadlock()
The text was updated successfully, but these errors were encountered: