search

puhep / pudb

Purdue CMS FPix Database
0 stars 0 forks source link

Promoting a module to installed on blade #95

Closed merkelp closed 8 years ago

merkelp commented 8 years ago

Hi, I was able to do this with this module: http://www.physics.purdue.edu/cmsfpix/Submission_p/assembly/bbm.php?name=P-B-7-29 ( a little annoying side effect was that after submitting this new status, the page just went blank and I had to double back to get anywhere). There is no checkmark next to this new status. It would be nice if the information of which disk and blade this was installed on was also visible on this page.

However, I was not able to do the same for another module: http://www.physics.purdue.edu/cmsfpix/Submission_p/assembly/bbm.php?name=P-B-5-34 Is this because previous steps have not yet been done?

Thanks, Petra

merkelp commented 8 years ago

and for this module I can not set the 'next testing step': http://www.physics.purdue.edu/cmsfpix/Submission_p/submit/fullSubmit.php?name=P-B-4-06

gneeser commented 8 years ago

Petra, As for the second issue, setting the next testing step on P-B-4-06, I was able to set the next testing step. Were you logged in at the time? If so, did you enter your username? If the user field is not filled, the page will not apply any changes made. Adding error messages for items like that is on my to-do list. If you did do these things, then I'll take a closer look and try to see what could have happened.

For promoting P-B-5-34, your suspicion was correct. Unless the Next Testing Step is set to 'Ready for Mounting' (meaning that the assembly step is also 'Ready for Mounting') users are not able to promote the module to On Blade. This in turn cannot be set unless the module has been fully assembled - meaning that its assembly status must be 'shipped.'

I'll add a checkbox and see about the issue after submitting the new status. Further, I'll add the info about where the module is on blade.

Best, Greg

merkelp commented 8 years ago

Hi Greg,

On 11/10/15 2:24 PM, gneeser wrote:

Petra, As for the second issue, setting the next testing step on P-B-4-06, I was able to set the next testing step. Were you logged in at the time? If so, did you enter your username? If the user field is not filled, the page will not apply any changes made. Adding error messages for items like that is on my to-do list. If you did do these things, then I'll take a closer look and try to see what could have happened.

I was logged in (unless I got kicked out for some reason?), I first did the one module successfully, then failed with the others. I did put my name, that I am sure of.

For promoting P-B-5-34, your suspicion was correct. Unless the Next Testing Step is set to 'Ready for Mounting' (meaning that the assembly step is also 'Ready for Mounting') users are not able to promote the module to On Blade. This in turn cannot be set unless the module has been fully assembled - meaning that its assembly status must be 'shipped.'

I'll add a checkbox and see about the issue after submitting the new status. Further, I'll add the info about where the module is on blade.

— Reply to this email directly or view it on GitHub https://github.com/puhep/pudb/issues/95#issuecomment-155555131.

NickHinton commented 8 years ago

Hi Petra,

We have not been able to replicate your problem on P-B-4-06. Both Greg and I were able to update the next testing status on different machines (and multiple modules). Can you try to replicate the failure?

The blank page that displays after updating a module's assembly status is a global issue that we are working on. However, we believe any submitted updates will be successful.

Thanks, Nick

khan62 commented 8 years ago

The blank page issue has been fixed.

merkelp commented 8 years ago

Hi Nick, I will try again, maybe I got logged out for some reason.

Thanks for checking, Petra

Sent from my iPhone

On Nov 10, 2015, at 4:30 PM, NickHinton notifications@github.com wrote:

Hi Petra,

We have not been able to replicate your problem on P-B-4-06. Both Greg and I were able to update the next testing status on different machines (and multiple modules). Can you try to replicate the failure?

The blank page that displays after updating a module's assembly status is a global issue that we are working on. However, we believe any submitted updates will be successful.

Thanks, Nick

— Reply to this email directly or view it on GitHub.

merkelp commented 8 years ago

Hi, I tried again, and was now successful in mounting all four modules on blades. I guess I had just gotten logged out due to some glitch, or lost internet connection or something. Looks good now, thanks. Petra