Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] TARGET.Runtime >= RequestRuntime
- Date: Fri, 26 Jul 2019 12:43:57 +0200 (CEST)
- From: "Beyer, Christoph" <christoph.beyer@xxxxxxx>
- Subject: Re: [HTCondor-users] TARGET.Runtime >= RequestRuntime
Hi all,
I figured out that the below described behaviour starts with version 8.9.2-1 hence I did downgrade my remote submit hosts to keep my clients happy.
Need a fix or anything though ...
Best
Christoph
--
Christoph Beyer
DESY Hamburg
IT-Department
Notkestr. 85
Building 02b, Room 009
22607 Hamburg
phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx
----- UrsprÃngliche Mail -----
Von: "Christoph Beyer" <christoph.beyer@xxxxxxx>
An: "htcondor-users" <htcondor-users@xxxxxxxxxxx>
Gesendet: Mittwoch, 17. Juli 2019 14:48:18
Betreff: TARGET.Runtime >= RequestRuntime
Hi Todd et al,
this is probably rather a question for the developer or at last those who are aware of the source code I am afraid.
I do have some user using a python framework and by doing so they trigger the requirement 'TARGET.Runtime >= RequestRuntime' in the r jon requirement which results in stuck jobs as TARGET.Runtime is not set by default on our workernodes.
I had this issue before triggered by somone who by mistake did not put '+RequestRuntime = XXX' in his submit file but 'request_runtime = XXX' which obviously was easy to fix.
In the current case though I have no idea what triggers 'TARGET.Runtime >= RequestRuntime' to show up in the job requirement - hopefully someone can enlighten me :) (?)
Best
Christoph
--
Christoph Beyer
DESY Hamburg
IT-Department
Notkestr. 85
Building 02b, Room 009
22607 Hamburg
phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx