Bug 557787 - AI refuses to move when faced with losing situation.
Summary: AI refuses to move when faced with losing situation.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pychess
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-22 15:26 UTC by Jesse
Modified: 2010-12-03 23:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:59:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Saved game where AI refuses to move. (421 bytes, application/x-chess-pgn)
2010-01-27 14:45 UTC, Jesse
no flags Details

Description Jesse 2010-01-22 15:26:28 UTC
Description of problem:
The AI player will often refuse to move when faced with a losing situation and refuse requests of "Ask to move".


Version-Release number of selected component (if applicable):
Version: 0.8.2
Package: pychess-0.8.2-4.fc12.noarch


How reproducible:
The refusal to move happens in about one of every three games in which the AI is a few moves from losing the game.


Steps to Reproduce:
1. Open pychess
2. Play the game, forcing the AI into a poor situation.
3. The AI stops moving, but the interface is still interactive.

  
Actual results:
The AI player ruses to move. Any attempt to force it to move either has no results or causes the game engine to disconnect.


Expected results:
The AI should continue to play until the game is completed.


Additional info:
This bug happens fairly often (about once in every three games) but doesn't seem to fit any pattern other than the AI is in a losing position. It seems that when faced with few options, all of them leading to mate in a few moves, the engine will lock up. This leaves the GUI still functioning, but brings the game to a stand still.

Comment 1 Jesse 2010-01-27 14:45:39 UTC
Created attachment 387094 [details]
Saved game where AI refuses to move.

Here is a saved game from a match where the human player is white and the AI is black. The AI ran out the last three minutes of its time refusing to move.

Comment 2 Fedora Update System 2010-02-03 15:47:33 UTC
pychess-0.10-0.1.20100203svn.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/pychess-0.10-0.1.20100203svn.fc12

Comment 3 Fedora Update System 2010-02-05 01:18:10 UTC
pychess-0.10-0.1.20100203svn.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update pychess'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1432

Comment 4 Thomas Spura 2010-02-08 02:24:09 UTC
I could directly continue the game you saved as attachment, could you please test it too?

Comment 5 Jesse 2010-02-08 13:39:44 UTC
Restoring that game allowed me to continue play. Which makes for a fair work-around.

Comment 6 Thomas Spura 2010-02-10 11:33:58 UTC
So you consider this as 'fixed'? ;)

Sounds like that.

Can you reproduce such a refusing again?

Comment 7 Jesse 2010-02-10 12:51:48 UTC
No, I wouldn't consider saving a game ands restoring it as a "fix". It's a work-around, but the game should play through without freezing. The game locks up fairly often, about one in every three games it's losing, so I think there's something wrong.

Comment 8 Thomas Spura 2010-02-10 13:04:21 UTC
ok, leaving this open, till a real fix from upstream is implemented...

Comment 9 Fedora Update System 2010-02-11 14:56:17 UTC
pychess-0.10-0.1.20100203svn.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Bug Zapper 2010-11-04 00:13:31 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 12 Bug Zapper 2010-12-03 23:59:03 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.