IZ130: resource reservation test might not cover the intended test case
|Reported by:||joga||Owned by:|
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=130]
Issue #: 130 Platform: All Reporter: joga (joga) Component: testsuite OS: All Subcomponent: tests Version: current CC: None defined Status: NEW Priority: P2 Resolution: Issue type: DEFECT Target milestone: milestone 1 Assigned to: issues@testsuite QA Contact: joga URL: * Summary: resource reservation test might not cover the intended test case Status whiteboard: Attachments: Issue 130 blocks: Votes for issue 130: Vote for this issue Opened: Mon Jun 11 02:23:00 -0700 2007 ------------------------ The test system_tests/scheduler/resource_reservation covers resource reservation with parallel jobs. We had a memory leak in scheduler (IZ 2187), in code that should be covered by the resource reservation test, but when running the test with sge_schedd running in a memory debugger (e.g. insure), the memory leak was not found. When manually creating a situation where a reservation was done for a pe job (having many short sequential jobs and one parallel job with reservation), the memory leak was discovered by insure. This suggests, that the test does not really cover the intended scenario. A means to figure out if really a reservation was done, is to switch on profiling of scheduler, and look for the number of reservations done in the profiling output. This could even be done by testsuite. Run a 6.0u10 (where the bug shows up) cluster with scheduler in insure, fix the test in a way that the memory leak shows up in insure when running the resource reservation test.
Change History (0)
Note: See TracTickets for help on using tickets.