Bug 1473230 - The netbsd-periodic Jenkins job contains *many* core files in the archive on failure
The netbsd-periodic Jenkins job contains *many* core files in the archive on ...
Status: NEW
Product: GlusterFS
Classification: Community
Component: tests (Show other bugs)
mainline
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-20 05:27 EDT by Niels de Vos
Modified: 2017-07-20 05:27 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Niels de Vos 2017-07-20 05:27:41 EDT
Description of problem:

The https://build.gluster.org/job/netbsd-periodic/ job generates a .tgz on failure (when a new core was detected), but it also contains all the other cores that are under build/install/cores/ . This makes the archive larger than needed, and more difficult to find the correct core.

It would help tremendously if:
- old cores can be deleted before running the tests
- a backtrace is logged in the Jenkins console output (and maybe written to a 
  file in the archive), just like for centos6-regression

Note You need to log in before you can comment on or make changes to this bug.