[Bug 1084311] Re: modifies .uploaded time every time whoopsie starts

[C de-Avillez]

verified, using the steps in the description, that (1) current whoppsie
did not upload an updated crashdump, and (2) whoppsie from -proposed
*did* upload a newer crash.

Tagging verification-done.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1084311

Title:
  modifies .uploaded time every time whoopsie starts

Status in Ubuntu error tracker client (whoopsie):
  Fix Released
Status in “whoopsie” package in Ubuntu:
  Fix Released
Status in “whoopsie” source package in Quantal:
  Fix Committed

Bug description:
  [Impact]

  Every time whoopsie starts up it modifies the .uploaded file
  corresponding to a .crash file regardless of whether or not the .crash
  is newer than the .uploaded.  Subsequently, it is possible for some
  crashes not to be sent to daisy.

  [Test Case]

  1) Install xeyes if it is not already
  2) Execute the following command in a terminal:
  DISPLAY=:0 xeyes &; PID="$\!"; sleep 3; kill -SEGV $PID
  3) Watch /var/crash for a .crash, .upload and .uploaded files for xeyes
  4) Once all three have appeared stop whoopsie:
  sudo stop whoopsie
  5) Run the command from step 2 again
  6) Check /var/crash and ensure that you have a .crash file newer than the .uploaded file
  7) Execute the command:
  sudo CRASH_DB_URL=https://daisy.ubuntu.com whoopsie -f
  8) Check /var/crash for a .uploaded file newer than the .crash file and watch the whoopsie output noticing that there is no communication with daisy

  With the version from -proposed you'll notice in step 8 that you can
  see the xeyes crash report sent to daisy.

  [Regression Potential]
  It's possible that the report_dir variable is incorrect and that no crashes will be processed at all.  However, I've run the whoopsie test suite with no issues and making any application crash will quickly reveal the absence of a .uploaded file.

  It looks like whoopsie is modifying the .uploaded file corresponding
  to a crash report every time it runs:

  [  4:16PM ]  [ bdmurray at blacklightning:~ ]
   $ ls -lh /var/crash
  total 11M
  -rw------- 1 whoopsie whoopsie    0 Nov 28 16:11 _usr_bin_d-feet.1000.uploaded

  [  4:30PM ]  [ bdmurray at blacklightning:~ ]
   $ sudo service whoopsie stop

  [  4:30PM ]  [ bdmurray at blacklightning:~ ]
   $ sudo CRASH_DB_URL=http://localhost:8080 whoopsie -f
  online

  [  4:30PM ]  [ bdmurray at blacklightning:~ ]
   $ ls -lh /var/crash
  total 11M
  -rw------- 1 whoopsie whoopsie    0 Nov 28 16:30 _usr_bin_d-feet.1000.uploaded

  As I was trying to trouble shoot the upload process (before I rebooted
  I had .crash file that was newer than the .uploaded file) I found this
  a bit confusing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/whoopsie/+bug/1084311/+subscriptions