Web lists-archives.com

Weird (seemingly flakey) p4 breakage in t9833




Hi Luke,

in a private Azure Pipeline (sorry...) I noticed an intermittent problem
in the p4 tests on osx-gcc.

I would point you to a public log, but the Azure Pipelines support *just*
made it to next, so I *just* set up a public one targeting anything else
than my `vsts-ci` branch, at
https://dev.azure.com/gitgitgadget/git/_build/index?definitionId=6. And
those builds do not show that problem, so it must be a flakey test.

But maybe you can spot anything familiar from the log?

-- snip --
[...]
++ P4TICKETS='/Users/vsts/agent/2.146.0/work/1/s/t/trash
directory.t9833-errors/cli/tickets'
++ P4USER=short_expiry_user
++ echo password
++ p4 login
Enter password: 
User short_expiry_user logged in.
Perforce db files in '.' will be created if missing...
++ cd '/Users/vsts/agent/2.146.0/work/1/s/t/trash
directory.t9833-errors/git'
++ git p4 sync
++ true
+++ time_in_seconds
+++ cd /
+++ /usr/bin/python -c 'import time; print(int(time.time()))'
++ test 1549411312 -gt 1549411605
++ sleep 1
Perforce db files in '.' will be created if missing...
failure accessing depot: perforce ticket expires in 1 seconds
Performing incremental import into refs/remotes/p4/master git branch
Depot paths: //depot/
error: last command exited with $?=1
++ true
+++ time_in_seconds
+++ cd /
+++ /usr/bin/python -c 'import time; print(int(time.time()))'
++ test 1549411314 -gt 1549411605
++ sleep 1
not ok 6 - git operation with expired ticket
#	
#		P4TICKETS="$cli/tickets" &&
#		P4USER=short_expiry_user &&
#		echo "password" | p4 login &&
#		(
#			cd "$git" &&
#			git p4 sync &&
#			sleep 5 &&
#			test_must_fail git p4 sync 2>errmsg &&
#			grep "failure accessing depot" errmsg
#		)
#	
-- snap --

BTW I find it very odd to see a `sleep 1` in the trace but not in the
snippet (there is only a `sleep 5` instead, which I fail to see in the
trace). Odd?

Ciao,
Johannes