patchbot vs sagedev.py doctest

[Thierry]

Hi,

i am trying to run some patchbots within a VM, i am using a ptestlong-ed
version of Sage 6.7, but when the patchbot runs tests, i got an error
during the test of sagedev.py (while i have no error with make ptestlong):

sage -t --long --warn-long 75.9 src/sage/dev/sagedev.py
**********************************************************************
File "src/sage/dev/sagedev.py", line 897, in
sage.dev.sagedev.SageDev.checkout_branch
Failed example:
dev.git.echo.stash('apply')
Exception raised:
Traceback (most recent call last):
File
"/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 496, in
_run
self.compile_and_execute(example, compiler, test.globs)
File
"/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 858, in
compile_and_execute
exec(compiled, globs)
File "<doctest sage.dev.sagedev.SageDev.checkout_branch[18]>", line 1,
in <module>
dev.git.echo.stash('apply')
File
"/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/dev/git_interface.py",
line 1199
, in meth
return self(git_cmd, *args, **kwds)
File
"/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/dev/git_interface.py",
line 227,
in _execute
raise GitError(exit_code, cmd, stdout, stderr)
GitError: git returned with non-zero exit code (1) for "git -c
user.email=d...@test.test -c user.name=doctest stash apply".
output to stderr: refs/stash@{0} is not a valid reference
**********************************************************************
File "src/sage/dev/sagedev.py", line 915, in
sage.dev.sagedev.SageDev.checkout_branch
Failed example:
dev.checkout(branch="branch1")
Expected:
The following files in your working directory contain uncommitted changes:
<BLANKLINE>
tracked
<BLANKLINE>
Discard changes? [discard/Cancel/stash] discard
On local branch "branch1" without associated ticket.
<BLANKLINE>
# Use "sage --dev merge" to include another ticket/branch.
# Use "sage --dev commit" to save changes into a new commit.
Got:
On local branch "branch1" without associated ticket.
<BLANKLINE>
# Use "sage --dev merge" to include another ticket/branch.
# Use "sage --dev commit" to save changes into a new commit.
**********************************************************************


If, on the same machine, if test the same file by hand, i have no problem:

./sage -t --long src/sage/dev/sagedev.py
Running doctests with ID 2015-05-20-21-47-49-c8392758.
Git branch: patchbot/ticket_merged
Doctesting 1 file.
sage -t --long --warn-long 76.3 src/sage/dev/sagedev.py
[868 tests, 39.35 s]
----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 39.5 seconds
cpu time: 7.7 seconds
cumulative wall time: 39.3 seconds


The same problem appears on Debian/Ubuntu, 32/64 bits, various releases,
see http://patchbot.sagemath.org/ticket/0/

Any idea of what could be wrong here ?

Ciao,
Thierry

[Frédéric Chapoton]

Hello,

I would like to second this demand. I have not been able to understand what is going wrong here.

if somebody understanding the dev scripts could say a word, that would be nice.. This issue is preventing two patchbot instances to run,

and we are currently lacking them much.

Frederic

[Volker Braun]

Its possible that this is just a symptom of a corruption that happened elsewhere.

The patchbot should perhaps run some clean-up on the git repo before each build attempt to start from a known state. E.g.

     git fsck --full

     git stash clear