Re: [HTCondor-users] Difference in path interpretation for queue from when using max_materialize

[Jaime Frey <jfrey@xxxxxxxxxxx>]

I can confirm this behavior and it looks like a bug to me. The late-materialization code appears to be skipping a check for whether the executable is an absolute path.

 - Jaime

On Feb 12, 2026, at 3:16âAM, Carles Acosta <cacosta@xxxxxx> wrote:

Hello,

We have a user submitting jobs using queue <var> from <list_file> in combination with max_materialize.

The submit file looks something like this:

exec = $(exec)
...

queue exec from list_exec.txt

When we submit without max_materialize, the jobs run correctly. HTCondor correctly interprets the entries in the list as absolute paths to the executable.

However, when we add max_materialize=XX to the submit file, the jobs fail. It seems that with max_materialize, HTCondor considers the paths in the list as relative paths from the submission directory.

Is this behavior expected when using late materialization?

Thank you in advance for your help.

Best regards,

Carles

--

Carles Acosta i Silva

PIC (Port d'Informacià CientÃfica)

Campus UAB, Edifici D

E-08193 Bellaterra, Barcelona

Tel: +34 93 581 33 08

Fax: +34 93 581 41 10

http://www.pic.es 

AvÃs - Aviso - Legal Notice:  http://legal.ifae.es

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe

The archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-users/