Bug 1307965
| Summary: | qjson: FTBFS in rawhide | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | qjson | Assignee: | Rex Dieter <rdieter> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | jgrulich, projects.rg, rdieter | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-02-14 14:16:57 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1305208 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2016-02-13 22:12:24 UTC
Created attachment 1125956 [details]
build.log
Created attachment 1125957 [details]
root.log
Created attachment 1125958 [details]
state.log
%changelog * Sun Feb 14 2016 Rex Dieter <rdieter> 0.8.1-16 - %%check: make tests non-fatal xvfb-run isn't working "cannot connect to X server" (#1307965) Hmm, does xvfb-run set $DISPLAY properly? For instance, trojita.spec can not use xvfb-run. It may need a direct call to Xvfb with a parameter for $DISPLAY, see http://pkgs.fedoraproject.org/cgit/rpms/trojita.git/commit/?id=8a5cc9e0425bbfa9be7edfb9c27cdffaba070aaf xvfb-run -a is supposed to automatically find (and use) a free DISPLAY In short, you're working around the fact that xvfb-run doesn't run properly either. I guess I should file a bug Heh, turns out that on my rebuild to make the check non-fatal, the xvfb-run -a call ran properly (without error) |