Public bug reported: At the end of a particular run, stress-ng printed "unsuccessful run completed in 6109.56s", and returned exit code 2, but there was no "fail:" message anywhere prior to that. How can I determine which test actually failed?
The command line was: stress-ng --timestamp --verbose --verify --metrics brief --times --tz --sequential 0 --exclude efivar,resources --timeout 30 --copy-file-bytes 512M --fallocate-bytes 512M --fiemap-bytes 512M --hdd-bytes 512M --iomix-bytes 512M --msync-bytes 512M --readahead-bytes 512M --revio-bytes 512M --sync-file-bytes 512M I've uploaded the command output here: https://gist.github.com/glaebhoerl/130b0a4111fba0d6b7222d358b905f1f Using stress-ng-0.10 ** Affects: stress-ng (Ubuntu) Importance: Medium Assignee: Colin Ian King (colin-king) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841916 Title: stress-stack stressor terminates with segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1841916/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
