Skip to content

We leak non-integer time limits #383

@Matistjati

Description

@Matistjati

Output from running on latest version

   Slowest AC runtime: 5.115, setting timelim to 7 secs, safety margin to 14 secs
   PAC submission decreasing_priorities_UFQ.cpp (C++) OK: AC (26) [testcase: testcase secret/g7full/003-g1-3, CPU: 2.46s @ testcase secret/g6decreasing/076-g6-3]
   PAC submission full_solution.py (Python 3 w/Pypy) OK: AC (19) [testcase: testcase secret/g7full/037-g3-1, CPU: 21.15s @ testcase secret/g4line/055-g4-3]
   PAC submission increasing_priorities_UF_undo.cpp (C++) OK: AC (14) [testcase: testcase secret/g7full/002-g1-2, CPU: 2.54s @ testcase secret/g5increasing/066-g5-2]
   PAC submission line_st.cpp (C++) OK: AC (17) [testcase: testcase secret/g7full/001-g1-1, CPU: 2.54s @ testcase secret/g4line/055-g4-3]
WARNING PAC submission line_st.py (Python 3 w/Pypy) sensitive to time limit: limit of 5.833333333333334 secs -> WA, limit of 14.0 secs -> AC

Something seems a little strange to me: a fractional time limit of 5.833333333333334 and computed time limit of 7 secs don't seem consistent. So there is probably also a bug hiding somewhere.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions