{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":274473531,"defaultBranch":"master","name":"fio","ownerLogin":"safl","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2020-06-23T17:55:58.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/608657?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1700469505.0","currentOid":""},"activityList":{"items":[{"before":"414151108c1bd4c7eec0f06f465fa3ebb717d73b","after":"63f210e8c80bf9576264aca81780846e3b31b1a8","ref":"refs/heads/xnvme_includes","pushedAt":"2023-11-20T08:39:32.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"safl","name":"Simon A. F. Lund","path":"/safl","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/608657?s=80&v=4"},"commit":{"message":"engines/xnvme: only include entry-header ('libxnvme.h')\n\nThis changes how the xNVMe fio io-engine consumes the xNVMe library by\nonly including the library-entry header \"libxnvme.h\".\n\nFrom version 0.7.0 the xNVMe API headers are refactored to drop header\nguards on the individual headers and abide by the idiom of \"headers must\nnot include other headers\".\n\nThe exception is the library-entry header \"libxnvme.h\". The\nlibrary-entry-header includes all headers provided with xNVMe, which is\na convenient approach to consuming the library. One where, in case the\nAPI namespace grows or shrinks, then the xNVMe fio io-engine need not\nchange how it includes xNVMe.\n\nHowever, since fio has consumed the main-entry header and individual\nheaders, xNVMe has held back on removing the guards on _nvm, _zns, and\n_spec to avoid breaking the xNVMe fio engine. They will eventually be\ndeprecated. Thus, this change to consume xNVMe in the manner intended\nfrom version v0.7.0 and onwards.\n\nSigned-off-by: Simon A. F. Lund <simon.lund@samsung.com>","shortMessageHtmlLink":"engines/xnvme: only include entry-header ('libxnvme.h')"}},{"before":null,"after":"414151108c1bd4c7eec0f06f465fa3ebb717d73b","ref":"refs/heads/xnvme_includes","pushedAt":"2023-11-20T08:38:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"safl","name":"Simon A. F. Lund","path":"/safl","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/608657?s=80&v=4"},"commit":{"message":"engines/xnvme: only include entry-header ('libxnvme.h')\n\nThis changes how the xNVMe fio io-engine consumes the xNVMe library by\nonly including the library-entry header \"libxnvme.h\".\n\nFrom version 0.7.0 the xNVMe API headers are refactored to drop header\nguards on the individual headers and abide by the idiom of \"headers must\nnot include other headers\".\n\nThe exception is the library-entry header \"libxnvme.h\". The\nlibrary-entry-header includes all headers provided with xNVMe, which is\na convenient approach to consuming the library. One where, in case the\nAPI namespace grows or shrinks, then the xNVMe fio io-engine need not\nchange how it includes xNVMe.\n\nHowever, since fio has consumed the main-entry header and individual\nheaders, xNVMe has held back on removing the guards on _nvm, _zns, and\n_spec to avoid breaking the xNVMe fio engine. They will eventually be\ndeprecated. Thus, this change to consume xNVMe in the manner intended\nfrom version v0.7.0 and onwards.\n\nSigned-off-by: Simon A. F. Lund <simon.lund@samsung.com>","shortMessageHtmlLink":"engines/xnvme: only include entry-header ('libxnvme.h')"}},{"before":"ecba19b6b71a32b8f5d9f25fae13c8804846c84f","after":"afdde534004397ba1fb00ccc6f5906fa50dd667f","ref":"refs/heads/master","pushedAt":"2023-11-20T08:37:03.000Z","pushType":"push","commitsCount":1360,"pusher":{"login":"safl","name":"Simon A. F. Lund","path":"/safl","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/608657?s=80&v=4"},"commit":{"message":"t/jobs/t0012.fio: make this job time_based\n\nFrom time to time we see failures (especially on Windows) with this test\nbecause one of its jobs does not run long enough. Make the jobs run for\nthis test time_based so that they run for a minimum of 12s.\n\nExample error output:\n\nDEBUG:root:sample 0: job1 iops=343858.0 job2 iops=1719327.0 job3 iops=3438690.0 job3/job2=2.000 job3/job1=10.000\nDEBUG:root:sample 1: job1 iops=682225.0 job2 iops=3411146.0 job3 iops=6822273.0 job3/job2=2.000 job3/job1=10.000\nDEBUG:root:sample 2: job1 iops=1019335.0 job2 iops=5096697.0 job3 iops=10193375.0 job3/job2=2.000 job3/job1=10.000\nDEBUG:root:sample 3: job1 iops=1367550.0 job2 iops=6837771.0 job3 iops=13675524.0 job3/job2=2.000 job3/job1=10.000\nDEBUG:root:sample 4: job1 iops=1704137.0 job2 iops=8520706.0 job3 iops=17041393.0 job3/job2=2.000 job3/job1=10.000\nDEBUG:root:sample 5: job1 iops=2056314.0 job2 iops=10281595.0 job3 iops=20563173.0 job3/job2=2.000 job3/job1=10.000\nDEBUG:root:sample 6: job1 iops=2399343.0 job2 iops=11996744.0 job3 iops=23993468.0 job3/job2=2.000 job3/job1=10.000\nDEBUG:root:Test 12 exception:\nTraceback (most recent call last):\n  File \"D:\\a\\fio\\fio\\t\\fiotestlib.py\", line 465, in run_fio_tests\n    test.check_result()\n  File \"D:\\a\\fio\\fio\\t\\run-fio-tests.py\", line 180, in check_result\n    iops3 = iops3 + float(iops_files[2][i].split(',')[1])\nTest 12 FAILED: list index out of range t0012.fio\nIndexError: list index out of range\n\nSigned-off-by: Vincent Fu <vincent.fu@samsung.com>","shortMessageHtmlLink":"t/jobs/t0012.fio: make this job time_based"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADsxdfMAA","startCursor":null,"endCursor":null}},"title":"Activity · safl/fio"}