Skip to content

Bug: max-memory assumes bytes instead of megabytes #79

@fgvieira

Description

@fgvieira

When using (at least) the torque adapter it seems that the memory is assumed to be in bytes, even though the help says that --max-memory is in megabytes.

I submitted a job asking for --max-memory 1024, and it shows as:

                                                                                  Req'd       Req'd       Elap
Job ID                  Username    Queue    Jobname          SessID  NDS   TSK   Memory      Time    S   Time
----------------------- ----------- -------- ---------------- ------ ----- ------ --------- --------- - ---------
32678102                user        batch    job.reads_s      0      1     4      1024b     10:00:00  C       --

Is --max-memory supposed to be in bytes or megabytes?
Either way, would it be possible to allow for suffixes? For example, to specify 1gb or 1024mb.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions