Ticket 10853 - sacct edge case
Summary: sacct edge case
Status: RESOLVED DUPLICATE of ticket 2265
Alias: None
Product: Slurm
Classification: Unclassified
Component: User Commands (show other tickets)
Version: 20.11.3
Hardware: Linux Linux
: --- 4 - Minor Issue
Assignee: Marcin Stolarek
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2021-02-11 16:15 MST by Kris Whetham
Modified: 2021-02-15 01:59 MST (History)
5 users (show)

See Also:
Site: FB (PSLA)
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
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 ***