Bug 1457827
Summary: | Changes to the voting system on glusterfs 'master' branch | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Amar Tumballi <atumball> |
Component: | project-infrastructure | Assignee: | bugs <bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | bugs, gluster-infra, nigelb |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-20 06:09:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Amar Tumballi
2017-06-01 11:51:14 UTC
On master: 1) I'm thinking we just run the tests/basic folder? 2) Do you mean netbsd builds or regressions? The netbsd build (netbsd6-smoke) itself takes a short duration and is trivial to run. I recommend we keep that remove the NetBSD voting job. Additionally, are we running the netbsd regressions on a nightly basis now? 3) We already have a 32-bit compilation test in the form of strfmt_errors. Do we want more? On release branch: As far as I can see, this seems to be "keep going as we do right now". Are we removing netbsd voting regressions here too? for 'master': 1) tests/basic is good. 2) lets run netbsd6-smoke 3) We can run 'netbsd' job in nightly IMO. (doesn't matter much on 'master' branch decision now). On 'release-x.y': * For now, lets keep going as is, and see if any changes required later. All the changes have been made today. |