Bug 1609596
Summary: | "no build executed" failure in regression | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Atin Mukherjee <amukherj> |
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: | 2018-08-03 10:11:16 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
Atin Mukherjee
2018-07-30 01:20:48 UTC
The logs don't really indicate why patchset #7 did not trigger a smoke build. However, when patchset 8 was pushed, it triggered a message for patchset 7 to say "No Builds Exected". And then it went on to trigger the smoke builds. I will dig into Jenkins source code to figure out what happened. Well, that was traced down to something wrong with Jenkins. My strong suspicion is after the latest Java update, Jenkins started to behave inconsistently. We eventually had to do a restart and this has been good ever since. |