Ticket 10853

Summary:	sacct edge case
Product:	Slurm	Reporter:	Kris Whetham <kwhetham>
Component:	User Commands	Assignee:	Marcin Stolarek <cinek>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	4 - Minor Issue
Priority:	---	CC:	acontois, calebh, cinek, kwhetham, tim
Version:	20.11.3
Hardware:	Linux
OS:	Linux
Site:	FB (PSLA)	Slinky Site:	---
Alineos Sites:	---	Atos/Eviden Sites:	---
Confidential Site:	---	Coreweave sites:	---
Cray Sites:	---	DS9 clusters:	---
Google sites:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	NoveTech Sites:	---
Nvidia HWinf-CS Sites:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Tzag Elita Sites:	---
Linux Distro:	---	Machine Name:
CLE Version:		Version Fixed:
Target Release:	---	DevPrio:	---
Emory-Cloud Sites:	---

Description Kris Whetham 2021-02-11 16:15:33 MST

Hi Sched, 

Please find the reported edge case, we have CC'd Caleb for correspondence.

" Please open a bug with Sched and CC me.
There is an edge case with sacct where newlines are not escaped in the output which can break tools which try to parse this data. I suspect (but have not encountered) that this is also the case for pipe characters. For instance, on H2:

$ sacct -j 35248669 -P -o jobid,user,comment

JobID|User|Comment

35248669|celebio|ACL-laser2ccm-laser2fairseqpy-laser2-data-lr-0.001-laser2-a

lpha-0.0-ed

35248669.batch||

35248669.extern||

35248669.0||

Note how the first record spans two because the Comment field contains a newline."

Comment 4 Marcin Stolarek 2021-02-15 01:59:11 MST

I'm closing the ticket as a duplicate of an existing Severity 5 case.

cheers,
Marcin

*** This ticket has been marked as a duplicate of ticket 2265 ***