1221199 - Trying to send SMS under bad network coverage result in constant failure instead of waiting for network

Status: RESOLVED INVALID

(Firefox OS Graveyard :: RIL, defect)

Description

[:gerard-majax]

Basically it looks like bug 1152730 regressed: sending a SMS under bad network will fail instead of retrying enough.

Comment 1

[:gerard-majax]

My usecase is still the same: train, subway. This started I would say at worst two weeks ago, on master.

Comment 2

[Bevis Tseng[:bevis][:btseng](Exited)]

There is no change in sms sending since bug 1152730 is fixed in SmsService. I cannot see obvious change that causes regression.
set qawanted to see if there is any regression on this.
In addition, if this issue is reproducible, we need the adb logcat with "RIL Output in ADB" enabled in "Settings/Developer" for further analysis to see if the SmsService did retry when network was recovered but was still failure instead.

Comment 3

[:gerard-majax]

(In reply to Bevis Tseng[:bevistseng][:btseng] from comment #2)
> There is no change in sms sending since bug 1152730 is fixed in SmsService.
> I cannot see obvious change that causes regression.
> set qawanted to see if there is any regression on this.
> In addition, if this issue is reproducible, we need the adb logcat with "RIL
> Output in ADB" enabled in "Settings/Developer" for further analysis to see
> if the SmsService did retry when network was recovered but was still failure
> instead.

Bevis, please, try. Go somewhere without network, try to send a SMS you will see it easily.

Comment 4

[Bevis Tseng[:bevis][:btseng](Exited)]

(In reply to Alexandre LISSY :gerard-majax from comment #3)
> Bevis, please, try. Go somewhere without network, try to send a SMS you will
> see it easily.
No, I can't see it easily.
Just tested it 10 times with both Flame/Z3C in m-c build inside an elevator in B3.
Test steps:
1. make sure there is no signal.
2. send a SMS.
3. Check if the sms is kept in sending state.
4. Move elevator to 1F.

All messages were sent automatically after step 4.

BTW, bug 1152730 includes a marionette test case to ensure this functionality.
According to the information I have so far, I wouldn't say it's a regression.
Need more evidence to prove it.

Comment 5

[:gerard-majax]

I cannot get more evidence. This will stay like this.

Comment 6

[:gerard-majax]

(In reply to Bevis Tseng[:bevistseng][:btseng] from comment #4)
> (In reply to Alexandre LISSY :gerard-majax from comment #3)
> > Bevis, please, try. Go somewhere without network, try to send a SMS you will
> > see it easily.
> No, I can't see it easily.
> Just tested it 10 times with both Flame/Z3C in m-c build inside an elevator
> in B3.

I don't know what B3 is. 10 times might not be enough. It also depends on how long you stay out of coverage.

> Test steps:
> 1. make sure there is no signal.
> 2. send a SMS.
> 3. Check if the sms is kept in sending state.
> 4. Move elevator to 1F.
> 
> All messages were sent automatically after step 4.

How long between step 3 and 4 ?

> 
> BTW, bug 1152730 includes a marionette test case to ensure this
> functionality.
> According to the information I have so far, I wouldn't say it's a regression.

Believe what you want. My experience as a user clearly says it is a regression.

Comment 7

[Bevis Tseng[:bevis][:btseng](Exited)]

(In reply to Alexandre LISSY :gerard-majax from comment #6)
> (In reply to Bevis Tseng[:bevistseng][:btseng] from comment #4)
> > (In reply to Alexandre LISSY :gerard-majax from comment #3)
> > > Bevis, please, try. Go somewhere without network, try to send a SMS you will
> > > see it easily.
> > No, I can't see it easily.
> > Just tested it 10 times with both Flame/Z3C in m-c build inside an elevator
> > in B3.
> 
> I don't know what B3 is. 10 times might not be enough. It also depends on
> how long you stay out of coverage.
The 3rd floor underground.
> 
> > Test steps:
> > 1. make sure there is no signal.
> > 2. send a SMS.
> > 3. Check if the sms is kept in sending state.
> > 4. Move elevator to 1F.
> > 
> > All messages were sent automatically after step 4.
> 
> How long between step 3 and 4 ?
The longest one I try is about 10 minutes.
> 
> > 
> > BTW, bug 1152730 includes a marionette test case to ensure this
> > functionality.
> > According to the information I have so far, I wouldn't say it's a regression.
> 
> Believe what you want. My experience as a user clearly says it is a
> regression.