ae36712f888f6ba538eb4942e38ef2b8aaf6e6b4 |
|
25-Feb-2015 |
Gwendal Grignou <gwendal@chromium.org> |
disk_qual: disable sysinfo logger hook for StorageFio subtests When running hardware_StorageFio from another test, disable sysinfo logger scripts. Files collected before and after iteration (interupts, meminfo, slabinfo)... are not collected around the Fio call. Note that other files still are still collected, those in site_sysinfo.test_loggables or site_sysinfo.boot_loggables BUG=chromium:456195 TEST=Run StorageQualSuspend.quick on samus. Check where iteration.* directories are missing. Check there is still overall iteration directory present. Change-Id: I1f73b776b1149adaa77c38a49239aca10ae356f1 Signed-off-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/253643 Reviewed-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
d4594c8dbab4d49898bdeb10c21cf5a404153e5e |
|
23-Oct-2014 |
Gwendal Grignou <gwendal@chromium.org> |
TrimIntegrity: Fix an spelling error in the error case TestFailError should be TestFail BUG=None TEST=Check that is the only occurent of TestFailError. Change-Id: I0550070cf34e549794f5ca3465bc754ee1ef6b59 Signed-off-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/225158 Reviewed-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
58fde35f14d0b6101f517c6e45185e35230736fc |
|
30-Sep-2014 |
Gwendal Grignou <gwendal@chromium.org> |
Storage Test: Request use of use_sequence_number Given the test hardware_TrimIntegrity creates subjob and is triggered by a control file with time_length set, we must add a sequence number to directory otherwise we get messages like: TestError: hardware_StorageFio.before_trim already exists; multiple tests cannot run with the same subdirectory BUG=chromium:418334 TEST='test_that 192.168.1.15 StorageQualTrim.test' works. Change-Id: I7cfcae4874a3afd076bfce54874595401c8f87ce Signed-off-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/220407 Reviewed-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
8ba770dc9bcf2e60bf2db1b7128d7502df6e8e60 |
|
10-Jun-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
hardware_TrimIntegrity: Use hdparm determine trim feature Use hdparm to determine that we should raise TestFail or TestNAError when error occurs. Also change chunk size from 64K to 192K as we see some interesting behavior on some SSD. Condition for test result: - Trim command is not supported -> Target disk is a harddisk : TestNA -> Target disk is SCSI disk w/o trim : TestNA -> Otherwise : TestFail - Can not verify integrity of untrimmed data -> All case : TestFail - Trim data is not Zero -> SSD with RZAT : TestFail -> Otherwise : TestNA BUG=chromium:351900 TEST=Run with test_that for each condition Change-Id: If669809c9a4ccec0bceb8b2fd343cdcedff64197 Reviewed-on: https://chromium-review.googlesource.com/203307 Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org> Tested-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
db91566fe85feb8e8f35510e2775054875c26ad1 |
|
30-May-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
hardware_TrimIntegrity: Add to quick version to experimental suite Add quick version that test only 16MB of data instead of 1GB for the regular version. And add that to experimental suite. Also report error when trim does not supported in non hdd platform BUG=chromium:351900 TEST=Test pass on falco/peach_pit/parrot Change-Id: I0f082806ff9d04334f75f5c3a4659605935595f2 Reviewed-on: https://chromium-review.googlesource.com/202153 Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org> Tested-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
8b811e05e984afbdbdba57d0695279e3f28430de |
|
02-Jun-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
fio_util: Change description and graph name in perf_measurements We send FIO result perf data to chrome perf dashboard but the data from same platform with different internal disk (Example: falco 16G and 32G) get mixed in the same graph which makes the results to be not meaningful. This patch fixes that by separate each disk model/size to its own graph. Also move util to where it should be - Move fio_util from client/common_lib to client/bin - Move get_disk_size() from site_utils to base_utils BUG=chromium:379468 TEST=Run in falco/peach_pit. Get desired result in perf_measurements Change-Id: I50518ce541cb4b2fc21b67db1bbd5de82ddecc6d Reviewed-on: https://chromium-review.googlesource.com/202331 Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org> Tested-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
b20041adbcfd14abec85cc385d400ac01d1f7be3 |
|
22-Apr-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
hardware_TrimIntegrity: Add booting from USB test Modify test to make it suitable to test when booting from USB and add ability to test full size of internal drive. BUG=chrome-os-partner:27472 TEST=Run with test_that, test passed. Change-Id: Ic9e00797dc926b1daee2c80882fd689be4037bec Reviewed-on: https://chromium-review.googlesource.com/196375 Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org> Tested-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
540af155fcd1016257478c22de8828b449d18085 |
|
20-May-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
autotest: Add common code for disk related function. Add the following functions in site_utils and modify current client tests to use function in the utils instead of their own implementation. Also move get_fixed_dst_drive from utils to site_utils as this function is ChromeOS specific. - Get root device - Get root partition - Get spare root partition for testing - Check whether system is booted from internal disk or not - Get disk/partition size BUG=chromium:375396 TEST=Test affected function (listed below) with test_that. hardware_Badblocks, hardware_DiskSize, hardware_Smartctl, hardware_StorageFio, hardware_StorageTrim, hardware_TrimIntegrity, power_Consumption, platform_RootPartitionsNotMounted Change-Id: I2c3ea95a5d603e3700115006d77db897ab2847e5 Reviewed-on: https://chromium-review.googlesource.com/200627 Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Tested-by: Puthikorn Voravootivat <puthik@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
3f8eadd373c9ec8a74b38b255578b81c02f0f704 |
|
18-Feb-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
hardware_TrimIntegrity: Report trim not supported as a failure / refactor Now that we enable trim in eMMC part, the test should be failed when IOCTL reports that trim command is not supported. Also reorder command a bit to calculate hash for zero/one stream before measure the read speed. Fix a bug in calculating hash for one stream. BUG=chromium:329736 TEST=Tested in falco. Test passed. Change-Id: I622794168f5c61a3fd7929c20303226c3b467723 Reviewed-on: https://chromium-review.googlesource.com/187000 Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org> Tested-by: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
6e0beb3e275aa503c1eddf0eb79fa5c2ad888b7b |
|
23-Jan-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
hardware_TrimIntegrity: Compare read speed before/after trim. Use FIO to measure 4K random read QD32 performance before / after trim in hardware_TrimIntegrity. Device that doing trim properly should report some speed difference because we don't need to access NAND when read from trimmed LBA. BUG=chromium:329736 TEST=Tested in falco. Tested passed. Result shows that median read latency is 4x better. Change-Id: I76fe8a27c49e8eacc782e5c2cbcadc8e24bad7bd Reviewed-on: https://chromium-review.googlesource.com/183677 Tested-by: Puthikorn Voravootivat <puthik@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|
79a010971e2d9c053130202a2ad35eca4081762a |
|
23-Jan-2014 |
Puthikorn Voravootivat <puthik@chromium.org> |
Autotest: Add new test to verify data integrity when using trim command Add new hardware_TrimIntegrity test. This test will write 1 GB of data and verify that trimmed data are gone and untrimmed data are unaffected. The verification will be run in 5 passes with 0%, 25%, 50%, 75%, and 100% of data trimmed. This test will raise an error only when untrimmed data are corrupt. It will also report that trimmed data is zero'ed or not. If the target device does not support trim, this test will log about that and exit without raising an error. BUG=chromium:329736 TEST=Tested in link, falco, pit. Test passed. Result show that trimmed data are zero'ed in falco, did not change in link and ioctl does not support trim command in pit. Change-Id: Ida23cc9aa05b639f1329236f0f6494c413fa55d0 Reviewed-on: https://chromium-review.googlesource.com/183712 Tested-by: Puthikorn Voravootivat <puthik@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Commit-Queue: Puthikorn Voravootivat <puthik@chromium.org>
/external/autotest/client/site_tests/hardware_TrimIntegrity/hardware_TrimIntegrity.py
|