Bug 1473230 - The netbsd-periodic Jenkins job contains *many* core files in the archive on failure
Summary: The netbsd-periodic Jenkins job contains *many* core files in the archive on ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-20 09:27 UTC by Niels de Vos
Modified: 2018-09-18 08:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-18 08:14:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Niels de Vos 2017-07-20 09:27:41 UTC
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

Comment 1 Amar Tumballi 2018-09-18 08:14:15 UTC
The job is not running anymore, and not planning to support complete regression on NetBSD for now.


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