whoopsie creates a .uploaded file when uploading the core dump fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
whoopsie (Ubuntu) |
Triaged
|
High
|
Unassigned |
Bug Description
$ sudo CRASH_DB_URL=https:/
f │··
Using lock path: /var/crash/
online │··
Parsing /var/crash/
Uploading /var/crash/
Sent; server replied with: No error │··
Response code: 200 │··
Sent; server replied with: No error │··
Response code: 502 │··
Upload of the core dump failed. │··
total 18M │··
-rw-r----- 1 bdmurray whoopsie 17M May 5 15:46 _usr_bin_
-rw-r----- 1 bdmurray whoopsie 613K May 8 13:14 _usr_lib_
-rw-r--r-- 1 root whoopsie 0 May 13 13:00 _usr_lib_
-rw------- 1 whoopsie whoopsie 0 May 13 13:00 _usr_lib_
This seems wrong to me.
Changed in whoopsie (Ubuntu): | |
importance: | Undecided → High |
Changed in whoopsie (Ubuntu): | |
status: | New → Triaged |
Well at least for the 502 error it does. I believe we expect that another user will report a crash with the same StacktraceAddre ssSignature and we ask them for a core dump.