SGE queue name is hard-coded #73

Activity

1. machshev commented on Nov 27, 2025

   

   machshev

   on Nov 27, 2025

   Collaborator

   More actions

   Thanks, yes this looks like a potential improvement. I've not got access to a SGE setup at the moment, so I'm not sure if this Launcher works or not?
2. machshev

   added

   enhancementNew feature or requestNew feature or request

   on Nov 27, 2025
3. machshev

   added the

   Enhancement

   issue type on Nov 27, 2025
4. Timmmm commented on Nov 27, 2025

   

   Timmmm

   on Nov 27, 2025

   Author

   More actions

   I had a go but tbh couldn't get it to work, and it seemed like it was losing non-zero exit codes somewhere and reporting jobs as passing when they definitely didn't.

   I think in a few months we'll want to get it working properly so I'll try again then (and maybe just rewrite the whole thing...).

   👍React with 👍1Reacted by James McCorrie
5. AlexJones0 commented on May 14, 2026

   

   AlexJones0

   on May 14, 2026

   Contributor

   More actions

   FYI, we're planning to remove support for SGE since we have no way to easily test it and there isn't anyone actively using it at the moment - it seems to be broken to some degree. As mentioned in the PR that I linked, the Launcher interface that DVSim used to use has been overhauled since this issue was created and replaced with a new RuntimeBackend interface which should work better with e.g. batched job submission. So I think that if working SGE support is needed, you would ideally want to migrate the old SgeLauncher logic to the new interface.

   Note that with this new interface there is still a registry where you can hook in your own backend implementations, including adapters for the legacy Launcher interfaces. So another option might be fixing up the launcher locally and extending DVSim to use a custom SGE launcher.

   👍React with 👍1Reacted by Tim Hutt