htcondor bug: misinterpreted resource values

[mathisloevenich]

I've figured out a weard behavior.

Namely with having a termination event and resources like:

005 (107799.000.000) 07/11 20:45:50 Job terminated.
	(1) Normal termination (return value 1)
		Usr 0 00:03:14, Sys 0 00:00:41  -  Run Remote Usage
		Usr 0 00:00:00, Sys 0 00:00:00  -  Run Local Usage
		Usr 0 00:03:14, Sys 0 00:00:41  -  Total Remote Usage
		Usr 0 00:00:00, Sys 0 00:00:00  -  Total Local Usage
	0  -  Run Bytes Sent By Job
	0  -  Run Bytes Received By Job
	0  -  Total Bytes Sent By Job
	0  -  Total Bytes Received By Job
	Partitionable Resources :    Usage   Request Allocated 
	   Cpus                 :     0.11         1         1 
	   Disk (KB)            :     4    220200960 222312484 
	   Gpus                 :                            0
	   Memory (MB)          :   922        20480     20480 
...

it happens that by using the python bindings, the requested and allocated disk values get truncated.

The values that you get
with accessing the created htcondor.JobEvent do not equal the once shown above.

Namely event.get("RequestDisk") = 20200960 != 220200960 and
event.get("Disk") = 22312484 != 222312484

The above example is from a real created log file so it means that this bug comes from htcondor itself.
However this example is almost a year old, which means the behaviour could have changed with the newer versions.

It seems that htcondor does only read 8 characters for a resource and truncates the overhang.

I don't know if there is a fix for that and I hope it's more of a corner case.