Cannot start job in space with sub-spaces
2 posters
Page 1 of 1
Cannot start job in space with sub-spaces
I am trying to start a job on the QF_BV hierarchy that I have linked in my space (60284) and keep getting:
"http 500 - internal server error"
I am using the web-interface with the default settings, selecting "choose", "all in hierarchy" and then picking one of the solvers linked in the space with a configuration. After spending several seconds in "Creating your job, please wait. This will take some time for large jobs", I get the following error: "http 500 - internal server error". I succesfully started jobs in spaces that have no sub-spaces (QF_BV/brummayerbiere 60312) , but got the same error in spaces that do have sub-spaces (QF_BV/bruttomesso 60316).
"http 500 - internal server error"
I am using the web-interface with the default settings, selecting "choose", "all in hierarchy" and then picking one of the solvers linked in the space with a configuration. After spending several seconds in "Creating your job, please wait. This will take some time for large jobs", I get the following error: "http 500 - internal server error". I succesfully started jobs in spaces that have no sub-spaces (QF_BV/brummayerbiere 60312) , but got the same error in spaces that do have sub-spaces (QF_BV/bruttomesso 60316).
lianah- Posts : 11
Join date : 2014-04-23
Re: Cannot start job in space with sub-spaces
Hi, Liana. Thanks for reporting this. We have confirmed this bug (which Andy Reynolds also reported to us today). Hopefully we will be able to deploy a fix in the next day or two.
In the meantime, you should be able to work around this issue by using the "run space hierarchy" option when creating a job (you may have to reorganize your space a little to do this, since you need your solvers in the same subspaces as the benchmarks you want them to run on).
Aaron
In the meantime, you should be able to work around this issue by using the "run space hierarchy" option when creating a job (you may have to reorganize your space a little to do this, since you need your solvers in the same subspaces as the benchmarks you want them to run on).
Aaron
Similar topics
» Can't download large spaces
» Deployment: bug fix related to removing spaces
» Disk space limits
» Space XML upload error: name must have two characters
» How can the space leader use non-public solvers?
» Deployment: bug fix related to removing spaces
» Disk space limits
» Space XML upload error: name must have two characters
» How can the space leader use non-public solvers?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|