Project

General

Profile

Actions

Feature #2120

open

Provide peak memory usage for tools as well as time statistics

Added by Evgeny Novikov almost 13 years ago. Updated over 11 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Infrastructure
Start date:
12/21/2011
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

Night tests showed a change in a verdict for the vtest-0032-drivers-media-video-cafe_ccic.tar.bz2 driver from unsafe to unknown (because of a memory limit). So, I suggest that at least for RCV verifiers a statistics on memory usage (total and separated by components like time) will be rather helpful. It'll also provide a new point of view for RCV verifiers comparison.

The given issue hasn't high priority, of course. Especially, because of time resources are much more important for static verifiers in comparison with the memory ones.

Actions #1

Updated by Evgeny Novikov almost 13 years ago

Also there is such the problem arose with kbdrivers--0032-2.6.31.6--test-0032-2.6.31.6-verdict-unsafe-drivers--media--video--cafe_ccic.c.tar.bz2. It has the same suffix, so it may be absolutely the same driver... I see, that it is most likely the same driver but in the first case it's checked against 2.6.32.15 Linux kernel, while in the second case - 2.6.31.6.

Actions #2

Updated by Ilya Shchepetkov over 12 years ago

I removed this file from the test set for a while. Commit f9dd2f7 of master branch.

Actions #3

Updated by Evgeny Novikov over 11 years ago

  • Assignee changed from Vadim Mutilin to Vitaly Mordan
Actions

Also available in: Atom PDF