Opened 6 years ago

Last modified 5 years ago

#16372 new defect

Intermittent test failures with IPython history

Reported by: vbraun Owned by:
Priority: major Milestone: sage-6.4
Component: packages: standard Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Reported upstream. Developers acknowledge bug. Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description

Happens sometimes. IPython still doesn't know how to do atomic changes to the history, I guess:

sage -t --long src/sage/misc/displayhook.py
**********************************************************************
File "src/sage/misc/displayhook.py", line 23, in sage.misc.displayhook
Failed example:
    shell = get_test_shell()
Expected nothing
Got:
    ERROR! History file wasn't a valid SQLite database. It was moved to /home/buildslave-sage/slave/sage_git/dot_sage/ipython-1.2.1/profile_default/history-corrupt.sqlite and a new file created.
    ERROR! History file wasn't a valid SQLite database. It was moved to /home/buildslave-sage/slave/sage_git/dot_sage/ipython-1.2.1/profile_default/history-corrupt.sqlite and a new file created.

Change History (4)

comment:1 Changed 6 years ago by vbraun

  • Report Upstream changed from N/A to Reported upstream. Developers acknowledge bug.

Until the last IPython update we silenced that error in a Sage patch.

Upstream bug: https://github.com/ipython/ipython/issues/2845

comment:2 Changed 6 years ago by jhpalmieri

By the way, I don't know if this is related or can be fixed at the same time, but would it be possible for Sage doctesting to not add to the IPython history? I find it disconcerting to start a new session and to have odd commands appear in my history, due to doctesting.

comment:3 Changed 5 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:4 Changed 5 years ago by jdemeyer

Is this still relevant after #16745 and #17826?

Note: See TracTickets for help on using tickets.