Bug 692207

Summary:	Icecc get stuck during linking without any warning when ICECC_MAX_JOBS=1
Product:	[openSUSE] openSUSE 12.1	Reporter:	Karl Krach <mailinglists>
Component:	Basesystem	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	matz
Version:	Factory
Target Milestone:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Karl Krach 2011-05-06 08:51:56 UTC

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

The motivation was, that my VMWare was busy with managing the 22 remote compilations (-j22), so that the compile-jobs assigned to itself were the critical path. So I disabled the compilation on my host.

After some while I realized, that the linking does not work any more for native compilations. When cross-compiling, I don't use the ICECC for linking.

This costs me a lot of time and nerves. So could you add at least an warning:

     "building locally - but ICECC_MAX_JOBS=0 !!"

Thanks a lot,

Charly

Reproducible: Always

Steps to Reproduce:
1. Set ICECC_MAX_JOBS=0 in /etc/icecc/icecc.conf
2. Start compilation (make -j4)
   -> got stuck on linking
Actual Results:  
g++/icecc got stuck

Expected Results:  
At least an warning - better would be, if the linking is not affected by ICECC_MAX_JOBS - since it cannot be done remotely.

Comment 1 Stephan Kulow 2011-09-05 13:47:57 UTC

the scheduler decides this. The daemon could refuse to start, but if you disable your machine then you might as well expect it doesn't do anything - so unless you send me a patch I won't act here.