linux 4.13.0-37.42 ADT test failure with linux 4.13.0-37.42

Bug #1755245 reported by Kleber Sacilotto de Souza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Colin Ian King
tags: added: kernel-adt-failure
description: updated
Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote :

open FAILED
  stress-ng: debug: [20547] 4 processors online, 4 processors configured
  stress-ng: info: [20547] dispatching hogs: 4 open
  stress-ng: debug: [20547] cache allocate: default cache size: 16384K
  stress-ng: debug: [20547] starting stressors
  stress-ng: debug: [20548] stress-ng-open: started [20548] (instance 0)
  stress-ng: debug: [20547] 4 stressors spawned
  stress-ng: debug: [20549] stress-ng-open: started [20549] (instance 1)
  stress-ng: debug: [20550] stress-ng-open: started [20550] (instance 2)
  stress-ng: debug: [20551] stress-ng-open: started [20551] (instance 3)
  stress-ng: debug: [20547] process [20548] (stress-ng-open) terminated on signal: 9 (Killed)
  stress-ng: debug: [20547] process [20548] terminated
  stress-ng: debug: [20547] process [20549] (stress-ng-open) terminated on signal: 9 (Killed)
  stress-ng: debug: [20547] process [20549] terminated
  stress-ng: debug: [20550] stress-ng-open: exited [20550] (instance 2)
  stress-ng: debug: [20547] process [20550] terminated
  stress-ng: debug: [20547] process [20551] (stress-ng-open) terminated on signal: 9 (Killed)
  stress-ng: debug: [20547] process [20551] terminated
  stress-ng: info: [20547] unsuccessful run completed in 5.24s

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
assignee: nobody → Colin Ian King (colin-king)
importance: Undecided → Medium
status: Confirmed → In Progress
Revision history for this message
Colin Ian King (colin-king) wrote :

I've added more smarts into stress-ng to detect if the OOM killer killed these stressors and not mark it as failed

http://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=be1ef4b962e50ced6d80db7eaa03eee77b43e003

Changed in linux (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Colin Ian King (colin-king) wrote :

This failure was probably an OOM kill on the test, the stress-ng update as mentioned in comment #2 will be able to identify these and not mark them as a test failure.

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.