Bug 10076 - smoke test: possibly falsely passed r3395
: smoke test: possibly falsely passed r3395
Status: CLOSED FIXED
Product: SB Controller
Classification: Unclassified
Component: Product Quality
: unspecified
: PC Other
: -- critical (vote)
: 7.3.2
Assigned To: Wallace Lai
:
Depends on: 10075 10606
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-19 10:47 UTC by Ben Klaas
Modified: 2009-01-22 13:53 UTC (History)
5 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Klaas 2008-11-19 10:47:06 UTC
the secondary question to bug 10075 is how r3395 could have passed smoke tests if it's not possible to get through factory reset setup. 

It really (*really*) shouldn't have...

The smoke test macros should have run a wireless setup macro after the factory reset. If bug 10075 was hit, it could not have passed that test.

Wallace, can you re-run a smoke test with r3395 and confirm if it gets through factory reset and then if setupWPA passes?
Comment 1 Ben Klaas 2008-11-19 11:05:37 UTC
10075 has closed, but I still think this bug may be an issue. Wallace, if you can run a smoke test on r3395 and see if it passes, that would tell us whether that's the case.
Comment 2 Wallace Lai 2008-11-19 13:35:23 UTC
Factory Reset tests will be included in the AutoTestsSystem later.  It should not be part of the Smoke Tests.
Even when doing it manually, it is hit and miss the Jive connects back to router and Ray the first time after factory reset.  If it is included, very very few FW builds would ever make it through the Smoke Tests and uploaded for others to try.
Comment 3 Chris Owens 2008-11-20 15:23:49 UTC
This bug is marked as targeted for 7.3.  What needs to be done on this to ship 7.3?  It is not clear to me from the comments.
Comment 4 Ben Klaas 2008-11-20 15:46:47 UTC
A few days ago we pushed out a 7.3 firmware that could not be setup from factory reset. That seems very bad to me, which is why I targetted for 7.3.

See comment #2 for the other side of the story.

Comment 5 Wallace Lai 2008-11-20 18:29:27 UTC
The question is whether a Smoke Tests System should stop almost all the builds because of a known issue, or should it pass some of them to let other people test the areas not affected by the known bug.

This user just tried it.  Jive still does not connect back to router and Ray the first time after reset.
However, this user had decided to include it for tomorrow's run.  If the tests get stuck, decision will be made at that time as to what to do about this.
Comment 6 Richard Titmuss 2008-11-21 01:29:14 UTC
wallace, keep the tests as they are now, this close to the 7.3 release. Ben and/or myself will take a look at the smoke test when were in MV in a weeks time.

I'm re-targeting this to 7.3.1.
Comment 7 James Richardson 2008-12-19 08:02:33 UTC
Changing target to next release
Comment 8 Chris Owens 2008-12-22 09:28:01 UTC
Chris to work with Wallace on this issue for 7.3.2
Comment 9 Wallace Lai 2009-01-12 09:47:11 UTC
Bug 10606 is blocking this one.
Comment 10 Chris Owens 2009-01-15 15:45:41 UTC
Can we mark this bug as 'Fixed' now, Wallace?  thanks.
Comment 11 Wallace Lai 2009-01-15 17:13:48 UTC
Yes.  Marking as fixed.
The system will catch the bugs after factory reset.
Comment 12 James Richardson 2009-01-22 09:58:27 UTC
Fixed - Closed Message (SC)

This bug has been fixed in the 7.3.3 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 13 James Richardson 2009-01-22 13:53:46 UTC
Correction: SqueezeCenter version is 7.3.2