New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 748351 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
█ shuqianz@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

cyan-paladin:3302 timeout on security_Firewall, but test succeeds.

Project Member Reported by pho...@chromium.org, Jul 25 2017 
cyan-paladin:3302 failed

Builders failed on: 
- cyan-paladin: 
  https://luci-milo.appspot.com/buildbot/chromeos/cyan-paladin/3302

The suite logs on master (https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/130167373-chromeos-test/hostless/debug/) show the test timing out at 15:56 -

07/24 15:56:37.619 INFO |        server_job:0206| START	----	cave-paladin/R62-9775.0.0-rc3/bvt-inline/security_Firewall	timestamp=1500936997	localtime=Jul 24 15:56:37	
07/24 15:56:37.620 INFO |        server_job:0206| 	ABORT	----	cave-paladin/R62-9775.0.0-rc3/bvt-inline/security_Firewall	timestamp=1500936997	localtime=Jul 24 15:56:37	
07/24 15:56:37.620 INFO |        server_job:0206| END ABORT	----	cave-paladin/R62-9775.0.0-rc3/bvt-inline/security_Firewall	timestamp=1500936997	localtime=Jul 24 15:56:37

The logs for the test show that it completed 3 minutes earlier, at 15:53
(https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/130167464-chromeos-test/chromeos6-row2-rack18-host8/)

07/24 15:53:38.833 INFO |               job:0227| 		GOOD	security_Firewall	security_Firewall	timestamp=1500936818	localtime=Jul 24 15:53:38	completed successfully
07/24 15:53:38.842 INFO |               job:0227| 	END GOOD	security_Firewall	security_Firewall	timestamp=1500936818	localtime=Jul 24 15:53:38	
07/24 15:53:38.851 DEBUG|          base_job:0357| Persistent state client._record_indent now set to 1
07/24 15:53:38.855 DEBUG|          base_job:0384| Persistent state client.unexpected_reboot deleted
07/24 15:53:41.445 DEBUG|             utils:0212| Running 'rm -f /var/lib/cleanup_logs_paused'
07/24 15:53:41.482 INFO |               job:0227| END GOOD	----	----	timestamp=1500936821	localtime=Jul 24 15:53:41

Job on shard: http://chromeos-server108.mtv.corp.google.com/afe/#tab_id=view_job&object_id=130167464

Comment 1 by shuqianz@chromium.org, Jul 25 2017

Status: WontFix (was: Untriaged)
Here is the status log:

INFO	----	----	kernel=3.18.0-15875-g3df6ed5ad2be	localtime=Jul 24 15:53:18	timestamp=1500936798	
START	----	----	timestamp=1500936818	localtime=Jul 24 15:53:38	
	START	security_Firewall	security_Firewall	timestamp=1500936818	localtime=Jul 24 15:53:38	
		GOOD	security_Firewall	security_Firewall	timestamp=1500936818	localtime=Jul 24 15:53:38	completed successfully
	END GOOD	security_Firewall	security_Firewall	timestamp=1500936818	localtime=Jul 24 15:53:38	
END GOOD	----	----	timestamp=1500936821	localtime=Jul 24 15:53:41	

The test seems passed successfully. I will mark this bug as won't fix. Feel free to reopen it when it happens again.

Comment 2 by pho...@chromium.org, Jul 25 2017 

Right, it passed - why did the parent job think that it timed out?

Comment 3 by shuqianz@chromium.org, Jul 25 2017 

I fail to figure that out. I guess there may exist job state report latency? Not sure.

Comment 4 by pho...@chromium.org, Jul 25 2017 

That sounds plausible, but with 3 minutes between the test succeeding and the suite timing it out, there is probably an opportunity here to improve performance.
►

Sign in to add a comment