Bugzilla – Bug 10606
Ray does not always show up on Jive's player list after Jive's factory reset.
Last modified: 2009-04-06 15:46:40 UTC
Created attachment 4579 [details] messages log for this bug. FW: Both 7.4 and 7.3.2, and earlier releases Note: This bug must be fixed before Smoke Tests Sys can finish running the factory reset and WPA tests. Steps to Reproduce: 1. Have the Jive and Ray running in the standard wireless mode. 2. Perform factory reset on the Jive. 3. After connecting the Jive back to the router, the next step is to choose a player. 4. Notice the Ray wanted is routinely not listed this page. This user must routine press the LED button on the Ray to make it blink red before it shows on the Jive's list.
Created attachment 4580 [details] putty log for this bug.
Created attachment 4610 [details] Putty log for this bug.
This bug blocks 10076.
If the user select "Skip this step", the next screen will actually show the Rays. This is a must fix.
This works for me, I see all my players listed in the Choose Player page after a factory reset. I've done this five times. Once there was a short (couple of second) delay before all the players were shown on the screen. Maybe you need to extend the timeout used in the tests? Looking at the logs it would appear that the Jive is not connected to the network (or maybe connected to the wrong network), the log just shows repeated failures to connect to SN and no attempts to connect to any SCs. This would agree with what you are reporting. However if you are not connected to a network I'm not sure how you got to this stage? Can you double check the auto tests are configuring the network connection correctly. From the command line a useful check is 'wpa_cli status'. This should show the SSID, connection status and IP address if the jive is successfully connected. Also check connectivity by pinging from your SC host to the jive. How many players are connected to the test network? May be this bug is if you only have a single player. I didn't test that case. If you only have one player try connecting a couple of SBs to you SC, does that change things? It might also be useful if you could video the jive as it runs through the test, so I can verify what steps it's doing to get to the failure.
It is very certain that the Jive was already connected to the private test network. By going back to the networks page, the correct network is checked. James had also reproduced this bug in his own cube. There are currently three players attached to this network, two Jives and one new product. Interesting thing is, by clicking the "skip this step", the next page actually shows all the correct players. Also, sometimes the Jive does work perfectly after reset.
I see this error on 7.3 r3476, have not seen the error on 7.3 r3856 Wallace have you seen this on the latest builds?
This is seen on today's 7.4 build, jive_7.4_r3879.bin. This is preventing the build from passing the smoke tests after factory reset.
Jive factory only ray NOT in setup mode jive does not see ray on choose player menu must hit 'skip this step' ray seen on select player menu Richard: should the first player setup menu be blank if the player is already attached to a server? This is how it works on the manual tests I am running. I.E. the smoke test should <expect> the first screen to show 'skip this step' only if the ray is NOT in setup mode.
After the controller successfully connects to the router, the next menu page is "Set Up Receiver", instead of "Choose Player". The SetupWPAMacro.lua test script expects the "Choose Player" page without clicking the "Skip this step" item. Should the test script be changed to reflect that? If the script is changed, is it masking a problem?
Having discussed this with James we decided that it is a bug in the test system. If any receivers are waiting to be set up, then an addition "Setup Receiver" menu is display. This _only_ lists receivers in setup mode. If the test scripts find this page then they should advance to "Skip this step" before continuing the tests.
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
Failure with old automated test procedure.