seems to be passing now, argh..
# generalw
wide-energy-11069
11/16/2018, 7:16 AMseems to be passing now, argh..
e
enough-analyst-54434
11/16/2018, 1:49 PMThe most interesting lines were here:
Copy code
-------------- Captured stdout call --------------
logs/exceptions.15348.log +++
logs/exceptions.15348.log >>> timestamp: 2018-11-15T22:21:21.202556
logs/exceptions.15348.log >>> process title: python /home/travis/build/pantsbuild/pants/src/python/pants/bin/pants_loader.py --no-pantsrc --pants-workdir=/home/travis/build/pantsbuild/pants/.pants.d/tmp/tmpeh_txb0n.pants.d --kill-nailguns --print-exception-stacktrace=True publish.jar --local=/tmp/tmp1jyhdxa1 --no-dryrun --force --override=org.pantsbuild.testproject.publish#classifiers_2.11=1.2.3 testprojects/src/scala/org/pantsbuild/testproject/publish/classifiers
logs/exceptions.15348.log >>> sys.argv: ['/home/travis/build/pantsbuild/pants/src/python/pants/bin/pants_loader.py', '--no-pantsrc', '--pants-workdir=/home/travis/build/pantsbuild/pants/.pants.d/tmp/tmpeh_txb0n.pants.d', '--kill-nailguns', '--print-exception-stacktrace=True', 'publish.jar', '--local=/tmp/tmp1jyhdxa1', '--no-dryrun', '--force', '--override=org.pantsbuild.testproject.publish#classifiers_2.11=1.2.3', 'testprojects/src/scala/org/pantsbuild/testproject/publish/classifiers']
logs/exceptions.15348.log >>> pid: 15520
logs/exceptions.15348.log >>> Signal 15 was raised. Exiting with failure. (backtrace omitted)
logs/exceptions.15348.log >>>
logs/exceptions.15348.log >>> timestamp: 2018-11-15T22:21:23.030322
logs/exceptions.15348.log >>> process title: python /home/travis/build/pantsbuild/pants/src/python/pants/bin/pants_loader.py --no-pantsrc --pants-workdir=/home/travis/build/pantsbuild/pants/.pants.d/tmp/tmpeh_txb0n.pants.d --kill-nailguns --print-exception-stacktrace=True publish.jar --local=/tmp/tmp1jyhdxa1 --no-dryrun --force --override=org.pantsbuild.testproject.publish#classifiers_2.11=1.2.3 testprojects/src/scala/org/pantsbuild/testproject/publish/classifiers
logs/exceptions.15348.log >>> sys.argv: ['/home/travis/build/pantsbuild/pants/src/python/pants/bin/pants_loader.py', '--no-pantsrc', '--pants-workdir=/home/travis/build/pantsbuild/pants/.pants.d/tmp/tmpeh_txb0n.pants.d', '--kill-nailguns', '--print-exception-stacktrace=True', 'publish.jar', '--local=/tmp/tmp1jyhdxa1', '--no-dryrun', '--force', '--override=org.pantsbuild.testproject.publish#classifiers_2.11=1.2.3', 'testprojects/src/scala/org/pantsbuild/testproject/publish/classifiers']
logs/exceptions.15348.log >>> pid: 15348
logs/exceptions.15348.log >>> Exception caught: (sqlite3.IntegrityError)--pants-workdir--localenough-analyst-54434
11/16/2018, 1:55 PMThis is interesting because - afaict - neither the test nor the code under test does re-tries, meaning there is no obvious way the same two tmp dirs get re-used. When tmp dirs, uuids and millisecond times all match, it seems pretty clear - maybe - that the process was forked after reporting initialization and so two processes shared the same mem state. Perhaps @witty-crayon-22786 can comment here - he's the most familiar with the current state of the fork model and fork points.
w
wide-energy-11069
11/16/2018, 4:12 PMThanks for the pointer there! I will dig more
w
witty-crayon-22786
11/16/2018, 7:06 PMDanny should be able to help as well... I'm lightly available today due to some family stuff
w
wide-energy-11069
11/16/2018, 7:56 PM7 Views