{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":96542958,"defaultBranch":"master","name":"YDBTest","ownerLogin":"YottaDB","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2017-07-07T13:50:05.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/29870125?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1708713500.0","currentOid":""},"activityList":{"items":[{"before":"f5862ddc9d116756312d14ee42d8d97e37d5d0bd","after":"84405ae570af615a5e5541df1e0ee7adf98a3b6c","ref":"refs/heads/master","pushedAt":"2024-09-19T17:35:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] Enhance r130/ydb484 subtest to better test =, [, ]], ?, ], >, < operators (like 1fc9f3d7)\n\n* Just like 1fc9f3d7 enhanced the `r130/ydb484` subtest to better test `=\"\"` and `'=\"\"` operators,\n  this commit enhances the same subtest to better test a variety of other relational operators\n  all of which had optimizations done as part of YDB#1091 commits.","shortMessageHtmlLink":"[YDB#1091] Enhance r130/ydb484 subtest to better test =, [, ]], ?, ],…"}},{"before":"2b215a755c845dd8c7d31ce783b2d5d7e67ad3a7","after":"f5862ddc9d116756312d14ee42d8d97e37d5d0bd","ref":"refs/heads/master","pushedAt":"2024-09-19T16:54:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] New r202/bool_expr_gt-ydb1091 and r202/bool_expr_lt_ydb1091 subtests\n\n* In addition to adding the 2 new above mentioned subtests, this commit also adjusts the\n  perf numbers for various `r202/bool_expr*` subtests such that all values are r2.02 values.\n\n  Some of these values used to be GT.M V70005 numbers but after recent changes to YDB!1577,\n  the performance of YottaDB has become even better than GT.M for most operators (see\n  https://gitlab.com/YottaDB/DB/YDB/-/issues/1091#note_2119448697 for more details).\n\n  Therefore, it made sense to keep YottaDB r2.02 perf values as the baseline for all these\n  subtests as it keeps things consistent.","shortMessageHtmlLink":"[YDB#1091] New r202/bool_expr_gt-ydb1091 and r202/bool_expr_lt_ydb109…"}},{"before":"147dde21dd56d577a247e3501473cb55b77605b0","after":"2b215a755c845dd8c7d31ce783b2d5d7e67ad3a7","ref":"refs/heads/master","pushedAt":"2024-09-19T16:18:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] Fix occasional r202/bool_expr_pattern-ydb1091 subtest failure\n\n* I noticed the `r202/bool_expr_pattern-ydb1091` subtest failed in some x86_64 systems\n  with various diff like the following.\n\n  ```diff\n  222,225c222,225\n  < PASS: Test of [s x=(y?.\"1\")]\n  < PASS: Test of [s x=(y'?.\"1\")]\n  < PASS: Test of [s:(y?.\"1\") x=1]\n  < PASS: Test of [s:(y'?.\"1\") x=1]\n  ---\n  > FAIL: [Actual=5470103401] more than [Maxlimit=5401516411] instructions\n  > FAIL: [Actual=5470103633] more than [Maxlimit=5401522839] instructions\n  > FAIL: [Actual=5350107715] more than [Maxlimit=5275518344] instructions\n  > FAIL: [Actual=5420108998] more than [Maxlimit=5349022556] instructions\n  ```\n\n  ```diff\n  224,225c224,225\n  < PASS: Test of [s:(y?.\"1\") x=1]\n  < PASS: Test of [s:(y'?.\"1\") x=1]\n  ---\n  > FAIL: [Actual=5289170553] more than [Maxlimit=5275518344] instructions\n  > FAIL: [Actual=5359169167] more than [Maxlimit=5349022556] instructions\n  ```\n\n* Different systems with different processors gave different diffs like the above.\n  And some systems passed without any issues.\n\n* It is not clear why the number of instructions that `perf` reports varies by as much\n  as 6% across various x86_64 systems. But I did not spend a lot of time trying to figure\n  this out.\n\n* Instead I modified only just this subtest to allow for up to 10% variance in the limits\n  instead of the usual 5% in the other `r202/bool_expr_*` subtests.","shortMessageHtmlLink":"[YDB#1091] Fix occasional r202/bool_expr_pattern-ydb1091 subtest failure"}},{"before":"f7fae8dd3fec020554754d952c843d7101c387ba","after":"147dde21dd56d577a247e3501473cb55b77605b0","ref":"refs/heads/master","pushedAt":"2024-09-18T16:12:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] New r202/bool_expr_sortsafter-ydb1091 subtest to test that x]]y and x']]y boolean expressions are faster\n\n* The new `bool_expr_sortsafter-ydb1091` subtest implementation is based on the pre-existing\n  `bool_expr_follow-ydb1091` subtest.\n\n* Additionally, I noticed a couple of issues in r202/outref/bool_expr_pattern-ydb1091.txt so fixed those.\n  - Missing `##SUSPEND_OUTPUT PRO` line\n  - Using `z` instead of `.\"1\"`","shortMessageHtmlLink":"[YDB#1091] New r202/bool_expr_sortsafter-ydb1091 subtest to test that…"}},{"before":"e341e4e1b6447b572fb4b2386d725ac763cec08a","after":"f7fae8dd3fec020554754d952c843d7101c387ba","ref":"refs/heads/master","pushedAt":"2024-09-18T15:31:56.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] New r202/bool_expr_pattern-ydb1091 subtest to test that x?y and x'?y boolean expressions are faster\n\n* The new `bool_expr_pattern-ydb1091` subtest implementation is based on the pre-existing\n  `bool_expr_follow-ydb1091` subtest.","shortMessageHtmlLink":"[YDB#1091] New r202/bool_expr_pattern-ydb1091 subtest to test that x?…"}},{"before":"19cc71cca08a5cc21d166ebbeb5d1d86cc136f17","after":"e341e4e1b6447b572fb4b2386d725ac763cec08a","ref":"refs/heads/master","pushedAt":"2024-09-17T19:57:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] New r202/bool_expr_follow-ydb1091 subtest to test that x]y and x']y boolean expressions are faster\n\n* The new `bool_expr_follow-ydb1091` subtest implementation is based on the pre-existing\n  `bool_expr_contain-ydb1091` subtest.\n\n* While at this, I noticed a minor missing `ALLOW_OUTPUT` line in the following pre-existing reference\n  files at the very end so added that.\n  - r202/outref/bool_expr_contain-ydb1091.txt\n  - r202/outref/bool_expr_equ-ydb1091.txt\n\n* Additionally, addressed https://gitlab.com/YottaDB/DB/YDBTest/-/merge_requests/2093#note_2115383120,\n  a review comment from @shabiel (pasted below).\n  - Can you mention how you verified the output?\n  - Also mention why you didn't use curpro.\n\n  I noticed the same issue in the following 4 subtests (named `bool_expr*`) so addressed all of them\n  by updating the subtest driver .csh script as well as the subtest .txt reference file.\n  - r202/bool_expr_contain-ydb1091\n  - r202/bool_expr_equ-ydb1091\n  - r202/bool_expr_equnul-ydb777\n  - r202/bool_expr_follow-ydb1091","shortMessageHtmlLink":"[YDB#1091] New r202/bool_expr_follow-ydb1091 subtest to test that x]y…"}},{"before":"582141c1119748d6d31081a207c10a974fdf07f7","after":"19cc71cca08a5cc21d166ebbeb5d1d86cc136f17","ref":"refs/heads/master","pushedAt":"2024-09-15T22:06:46.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] New r202/bool_expr_contain-ydb1091 subtest to test that x[y and x'[y boolean expressions are faster\n\n* The new `bool_expr_contain-ydb1091` subtest is based on the pre-existing `bool_expr_equ-ydb1091`\n  subtest. While at this, I noticed some minor changes that can be done to the latter so took care\n  of those as well in this commit.","shortMessageHtmlLink":"[YDB#1091] New r202/bool_expr_contain-ydb1091 subtest to test that x[…"}},{"before":"e7c4d5589868d36e5f7370d1a214e653f349f79a","after":"582141c1119748d6d31081a207c10a974fdf07f7","ref":"refs/heads/master","pushedAt":"2024-09-13T04:23:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[#766] New v63007/gtm7318 subtest to test Audit Principal Device facility","shortMessageHtmlLink":"[#766] New v63007/gtm7318 subtest to test Audit Principal Device faci…"}},{"before":"32b605125636b05b7ff07a78c3ab6da1675e78da","after":"e7c4d5589868d36e5f7370d1a214e653f349f79a","ref":"refs/heads/master","pushedAt":"2024-09-12T13:26:16.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1091] Update r136/outref/ydb869.txt now that we get extra NUMOFLOW error messages (due to YDB@dd69a2c5)\n\n* There were 4 extra NUMOFLOW lines that showed up in the output of the `r136/ydb869` subtest after the\n  YDB@dd69a2c5 (YDB!1570) changes.\n\n* There was 1 extra NUMOFLOW line that showed up for each of the below lines.\n\n  **r136/inref/ydb869.m**\n  ```\n     25         write x=+\"1E47\"\n     26         write 0=+\"1E47\"\n      .\n     33         write x=-\"1E47\"\n     34         write 0=-\"1E47\"\n  ```\n\n* YottaDB r2.00 gave 3 NUMOFLOW lines for each of the above operations whereas YDB@dd69a2c5 gave\n  4 NUMOFLOW lines. Interestingly, GT.M gives only 1 NUMOFLOW line.\n\n  This is therefore a YottaDB misfeature that would be nice to fix. But it is not clear the fix is\n  straightforward as the compiler flow is very different for NUMOFLOW errors in GT.M vs YottaDB.\n\n  This discrepancy in the number of NUMOFLOW errors issued per M line is already captured at\n  https://gitlab.com/YottaDB/DB/YDBTest/-/merge_requests/1320#note_2012655551 and a todo is\n  tracked at https://gitlab.com/YottaDB/DB/YDB/-/issues/1018#note_2012656040.\n\n  The above example will also be recorded at the todo.\n\n* As part of this commit, the reference file will be updated to reflect the extra NUMOFLOW lines.\n\n* And an attempt will be made to try and get the NUMOFLOW lines down to 1 (like GT.M) as part of\n  merging GT.M V7.1-001 (YDB#1018).","shortMessageHtmlLink":"[YDB#1091] Update r136/outref/ydb869.txt now that we get extra NUMOFL…"}},{"before":"3adeb985836919fb9e11399f640f1968405fe567","after":"32b605125636b05b7ff07a78c3ab6da1675e78da","ref":"refs/heads/master","pushedAt":"2024-09-11T14:52:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"New r202/mumps_machine_lis-assertfailure subtest to test YDB@4d509b3e","shortMessageHtmlLink":"New r202/mumps_machine_lis-assertfailure subtest to test YDB@4d509b3e"}},{"before":"530cb8be931cdab21b3305aa23fe1333be4961f9","after":"3adeb985836919fb9e11399f640f1968405fe567","ref":"refs/heads/master","pushedAt":"2024-09-10T15:23:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[#636] Fix rare v70005/audit_logging-gtmf171004 failure (off-by-one-second)\n\nBackground\n----------\nRunning D_ALL tests caused the following symptom:\n```\naudit_logging-gtmf171004 took 00:00:00:04 from 2024.09.06.02.28.43.EDT to 2024.09.06.02.28.47.EDT : 208968 FAIL\n--- audit_logging-gtmf171004/audit_logging-gtmf171004.diff ---\n401c401\n< filename check: pass\n---\n> log filename check failed, BEFORE <= FILENAME_STAMP <= AFTER is not true: 1725604126 <= 1725604125 <= 1725604126\n```\n\nSee [this comment](https://gitlab.com/YottaDB/DB/YDBTest/-/merge_requests/2056#note_2092784103) for more.\n\nIssue\n-----\n\nThe three timestamp values, which are Unix epoch values (`BEFORE`, `FILENAME_STAMP`, `AFTER`) are generated by these lines:\n```\nset before_epoch=`date -u +\"%s\"`\nkill -HUP $pid\nset after_epoch=`date -u +\"%s\"`\n```\nThe `kill` command triggers background process `audit_listener` to rotate the log: it closes and renames actual log, appending timestamp to its name. The test finds the rotated file, and converts the date found in the filename to UTC epoch value, then checks the values for `BEFORE <= FILENAME_STAMP <= AFTER`.\n\nIn the failed tests (see above and the referenced comments), these values are `X`, `X-1`, `X` - surprisingly, `audit_listener` reports one second less than previously called `date(1)` command.\n\nThe `audit_listener` has no error, it uses simply `time(3)` to get the time, in the signal handler:\n```\nint switch_logfile(char *logfile)      // called from the signal handler\n{\n[...]\n  time(&switchtime);\n  [...]\n  timeptr = gmtime(&switchtime);\n```\n\nLooks like `time(3)` sometimes reports different values for different process groups (test script vs audit_listener), probably it could happen when the system time is getting adjusted by NTP daemon or such.\n\nFix\n---\nHoping that clock skew (so adjustment) does not exceed 1 sec, added adjusting of `BEFORE` value with -1. (Discussed that `AFTER` needs no adjustment.)","shortMessageHtmlLink":"[#636] Fix rare v70005/audit_logging-gtmf171004 failure (off-by-one-s…"}},{"before":"99196bbd96936bef0b1b6fa5cd13689c11c286ca","after":"530cb8be931cdab21b3305aa23fe1333be4961f9","ref":"refs/heads/master","pushedAt":"2024-09-10T13:42:03.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1097] New r202/fallintoflst-ydb1097 subtest to test FALLINTOFLST error is issued when falling through dotted DO lines","shortMessageHtmlLink":"[YDB#1097] New r202/fallintoflst-ydb1097 subtest to test FALLINTOFLST…"}},{"before":"58a0c8d55db4f3beb1d0d89216c368e33ffe82a5","after":"99196bbd96936bef0b1b6fa5cd13689c11c286ca","ref":"refs/heads/master","pushedAt":"2024-09-10T13:04:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"Fix 3 subtest failures due to ydb_temp_dist subdir now having an absolute path (due to 58a0c8d5)\n\n* Commit 58a0c8d5 set `gtm_dist` (and `ydb_dist`) env vars to an absolute path containing the\n  `ydb_temp_dist` subdirectory.\n\n* There were a few subtest reference files that relied on `ydb_temp_dist` being a relative path\n  and not an absolute path. Those subtests failed after 58a0c8d5.\n\n* They are fixed in this commit. All fixes are replacing a `ydb_temp_dist` usage with a\n  `##TEST_PATH##/ydb_temp_dist` usage.\n\n* While doing this, I noticed that a ##TEST_AWK regex usage in `v63003/outref/gtm8842.txt`\n  seemed unnecessary so removed it.","shortMessageHtmlLink":"Fix 3 subtest failures due to ydb_temp_dist subdir now having an abso…"}},{"before":"67fe6d2d3dcae037d1e9aac7a6e18dfa3c50f6d1","after":"58a0c8d55db4f3beb1d0d89216c368e33ffe82a5","ref":"refs/heads/master","pushedAt":"2024-09-09T15:02:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"Fix com/copy_ydb_dist_dir.csh to set gtm_dist to absolute path (lets ps -ef identify test output directory of audit_listener processes)\n\nBackground\n----------\n* While running a `ps -ef` on a system I noticed lots of left over processes from a test run of\n  the following form.\n\n  ```sh\n  $ ps -ef\n  .\n  .\n  user     27150     1  0 Sep06 pts/45   00:00:00 ydb_temp_dist/audit_listener tcp pid.txt log.txt 36008\n  .\n  .\n  ```\n\nIssue\n-----\n* That process showed up with the following file descriptors.\n\n  ```sh\n  $ ls -l /proc/27150/fd\n  total 0\n  lr-x------ 1 user grp 64 Sep  9 09:54 0 -> /dev/null\n  l-wx------ 1 user grp 64 Sep  9 09:54 1 -> '/testarea1/user/V998/tst_V998_R201_dbg_28_240906_114911_mGE/v70005_0_1/audit_logging-gtmf171004/log.txt (deleted)'\n  l-wx------ 1 user grp 64 Sep  9 09:54 2 -> '/testarea1/user/V998/tst_V998_R201_dbg_28_240906_114911_mGE/v70005_0_1/audit_logging-gtmf171004/log.txt (deleted)'\n  lrwx------ 1 user grp 64 Sep  9 09:54 3 -> 'socket:[342304433]'\n  ```\n\n* From that, it was clear this process corresponded to the test output directory with the name\n  `tst_V998_R201_dbg_28_240906_114911_mGE`.\n\n* In this case, the `audit_listener` process would have been started in line 133 below.\n\n  **v70005/u_inref/audit_logging-gtmf171004.csh**\n  ```sh\n    130         echo \"# launch $mode audit_listener\"\n    131         rm -f $aulogfile\n    132         if (\"$mode\" == \"tcp\") then\n    133                 ($gtm_dist/audit_listener tcp $aupidfile $aulogfile \\\n    134                         $portno &)\n  ```\n\n* The path would have been `$gtm_dist/audit_listener`. But since `$gtm_dist` got set to the\n  subdirectory `ydb_temp_dist`, that was the path which showed up in the `ps -ef` output.\n\nFix\n---\n* Setting `gtm_dist` to the absolute path (i.e. including the current directory too before adding\n  the subdirectory `ydb_temp_dist`) would clearly identify the process as belonging to the test\n  output directory `tst_V998_R201_dbg_28_240906_114911_mGE`.\n\n* Hence the fix is to add a `pwd` before setting `ydb_dist` and `gtm_dist` in `com/copy_ydb_dist_dir.csh`\n  as that is the script which is used to create the `ydb_temp_dist` subdirectory in the first place.\n\nMisc\n----\n* This commit is similar to prior commits cda912b6 and e5bd7f15.","shortMessageHtmlLink":"Fix com/copy_ydb_dist_dir.csh to set gtm_dist to absolute path (lets …"}},{"before":"f2c9e66840099be2c5eb3110502ef0ed8f32ec9b","after":"67fe6d2d3dcae037d1e9aac7a6e18dfa3c50f6d1","ref":"refs/heads/master","pushedAt":"2024-09-06T04:23:57.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[#614] New v70004/audit_mupip_nw_error-gtmf135381 subtest to test Audit MUPIP facility and network error handling in by the audit facility","shortMessageHtmlLink":"[#614] New v70004/audit_mupip_nw_error-gtmf135381 subtest to test Aud…"}},{"before":"79405235b76308c9f8437ba958bd226291671c54","after":"f2c9e66840099be2c5eb3110502ef0ed8f32ec9b","ref":"refs/heads/master","pushedAt":"2024-09-05T16:49:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDBTest#617] [V7.0-004] [GTM-F167559] New v70004/support_v6_database-gtmf167559 subtest to test MUPIP CREATE -V6\n\nRelease note http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V7.0-004_Release_Notes.html#GTM-F167559 says:\n\n> MUPIP CREATE creates V6 (V6.3-014) database files when the\n> environment variable gtm_db_create_ver is defined as [V]6,\n> or when the command line specifies: -V6. The -NOV6 command\n> line option allowing overrides a gtm_db_create_ver and creates\n> a V7 database file. This means this V7 release can operate\n> seamlessly with V6 databases. Prior V7 versions did not have\n> this support. (GTM-F167559)","shortMessageHtmlLink":"[YDBTest#617] [V7.0-004] [GTM-F167559] New v70004/support_v6_database…"}},{"before":"66ba96ea609db3d3fdfcabf2ac0fd7b005a4a37f","after":"79405235b76308c9f8437ba958bd226291671c54","ref":"refs/heads/master","pushedAt":"2024-09-05T16:28:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1080] Add YDBCurl installation check to ydbinstall plugin installation checks\n\nRelease note https://gitlab.com/YottaDB/DB/YDB/-/issues/1080 says:\n\n> The `--curl`, `--gui`, and `--allplugins` options of `ydbinstall` / `ydbinstall.sh`\n> install YDBCurl https://gitlab.com/ksbhaskar/YDBCurl, the YottaDB plugin for\n> libcurl https://curl.se/libcurl/ [ #1080 ]\n\nAdded `--curl` option to the list of existing options\n( `--gui` and `--allplugins` were already on the list).","shortMessageHtmlLink":"[YDB#1080] Add YDBCurl installation check to ydbinstall plugin instal…"}},{"before":"6bcfaeefe206ed23f88b01754510bac069fdc024","after":"66ba96ea609db3d3fdfcabf2ac0fd7b005a4a37f","ref":"refs/heads/master","pushedAt":"2024-09-02T08:43:22.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDBTest#636] [YDB#963] [V7.0-005] [GTM-F171004] New subtest v70005/audit_logging-gtmf171004 for checking Audit Logger features\n\nRelease note http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V7.0-005_Release_Notes.html#GTM-F171004 says:\n\n> GT.M audit logging facilities use tty to label the standard\n> input of the process. GT.M places tty=ttyname before the\n> command field in all audit log messages. If the standard input\n> at process startup is not terminal device, GT.M logs tty=0. In\n> addition, the audit facilities check for errors at the time of\n> closing a socket / terminating a connection and report them\n> with a GTM-E-SOCKCLOSE message to the operator log. The audit\n> logger/listener sample programs (downloadable from the A&O\n> Guide) switch their log files after receiving a SIGHUP signal.\n> The switched log file has a suffix \"_%Y%j%H%M%S\"\n> (yearjuliendayhoursminutesseconds) and the naming convention\n> is similar to what GT.M uses for switching journal files. FIS\n> recommends periodically switching logger files. Deleting an\n> active audit log file makes it lost to new processes, while\n> existing processes continue to use it, so FIS recommends\n> taking such a step. The sample programs have a Makefile.\n> Previously, the audit log facilities did not provide tty\n> information, did not check and report on errors during socket\n> close, the logger/listener programs did not implement a log\n> file switching mechanism, and those programs had no Makefile.\n> (GTM-F171004)","shortMessageHtmlLink":"[YDBTest#636] [YDB#963] [V7.0-005] [GTM-F171004] New subtest v70005/a…"}},{"before":"cecc9888f138f08f353a768268837ffb1688713d","after":"6bcfaeefe206ed23f88b01754510bac069fdc024","ref":"refs/heads/master","pushedAt":"2024-08-31T13:07:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1096] Fix r126/outref/ydb429.txt due to increase in default database parameters by YDB@c0c6471f","shortMessageHtmlLink":"[YDB#1096] Fix r126/outref/ydb429.txt due to increase in default data…"}},{"before":"cc4700d9b4090c8c738867cb4a3b7baf57293da2","after":"cecc9888f138f08f353a768268837ffb1688713d","ref":"refs/heads/master","pushedAt":"2024-08-30T18:32:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"New com/getDbVer.m utility for getting the database version of the specified .dat file\n\nFunction\n--------\nThis utility provides the DB version of the specified\n`.dat` file.\n\nEntry points:\n- print: print the version number (6, 7, or error)\n- get: entry point for calling from other M program\n\nImplementation\n--------------\nThe header of the `.dat` files contains a signature\nwhich identifies the file version:\n\n```\n$ hd v6.dat | head -n1\n00000000  47 44 53 44 59 4e 55 4e  58 30 33 00 00 10 00 00  |GDSDYNUNX03.....|\n\n$ hd v7.dat | head -n1\n00000000  47 44 53 44 59 4e 55 4e  58 30 34 00 00 10 00 00  |GDSDYNUNX04.....|\n```\n\nThe program checks its last character, and reports v6\non \"3\" and v7 on \"4\".\n\nSee also\n--------\nThe subtest added with MR https://gitlab.com/YottaDB/DB/YDBTest/-/merge_requests/2079\nchecks `mupip create` behaviour using various environment and\ncommand line argument settings, whether it creates v6 or v7\ndatabase as intended.","shortMessageHtmlLink":"New com/getDbVer.m utility for getting the database version of the sp…"}},{"before":"d7037fe8277df8741e7cf3989e359d1a0da6290d","after":"cc4700d9b4090c8c738867cb4a3b7baf57293da2","ref":"refs/heads/master","pushedAt":"2024-08-30T16:28:39.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#377] Enhance socket/mwebserver subtest to test TLS server side keys with no password\n\n* The `socket/mwebserver` subtest already tested a TLS web server where the server side was\n  generated using a key with a password.\n\n* But with YDB#77, we do not require keys to have a password. Therefore, this subtest has been\n  enhanced to also generate keys without a password. This choice is made randomly so the test\n  covers both use cases.","shortMessageHtmlLink":"[YDB#377] Enhance socket/mwebserver subtest to test TLS server side k…"}},{"before":"094c10793bb88a11454163748674e5cefbe74fe6","after":"d7037fe8277df8741e7cf3989e359d1a0da6290d","ref":"refs/heads/master","pushedAt":"2024-08-29T15:19:12.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1084] New r202/shebang-ydb1084 subtest to test shebang support for YottaDB","shortMessageHtmlLink":"[YDB#1084] New r202/shebang-ydb1084 subtest to test shebang support f…"}},{"before":"fc785e39abaed4baa4b3c9f2bd156074b70c42a3","after":"094c10793bb88a11454163748674e5cefbe74fe6","ref":"refs/heads/master","pushedAt":"2024-08-28T20:21:58.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#1084] Enhance sudo/ydb880 test to test ydbsh just like it already does ydb and gtm","shortMessageHtmlLink":"[YDB#1084] Enhance sudo/ydb880 test to test ydbsh just like it alread…"}},{"before":"4f39e7cd860e8d6fda10b80fa0a05f0253663246","after":"fc785e39abaed4baa4b3c9f2bd156074b70c42a3","ref":"refs/heads/master","pushedAt":"2024-08-28T03:39:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[#412] Fix r134/ydb785 test fails when YottaDB built with ASAN+GCC\n\nProblem\n---\n- `r134/ydb785` test fails when YottaDB built with ASAN+GCC.\n   More details in https://gitlab.com/YottaDB/DB/YDBTest/-/merge_requests/2053#note_2070679487\n\nFix\n---\n- Add `ydb_test_gover_lt_118` variable in `com/set_gtm_machtype.csh`\n  used in `com/setupgoenv.csh` for correct go build flag.\n  Previously, `ydb_test_gover_lt_118_or_rhel` variable was used in\n  `com/setupgoenv.csh` which is wrong.\n- Remove unnecessary `ASAN_CLANG_GOVER_LESS_THAN_118_OR_RHEL` from `com/outref.awk`\n  and from reference files in `r128/ydb478` and `r134/ydb785`","shortMessageHtmlLink":"[#412] Fix r134/ydb785 test fails when YottaDB built with ASAN+GCC"}},{"before":"4244c67b56f25d529b354b7e2f1faac4aa55c9ce","after":"4f39e7cd860e8d6fda10b80fa0a05f0253663246","ref":"refs/heads/master","pushedAt":"2024-08-27T17:04:05.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#999] Fix gtm_gbldir typo to gtmgbldir in ZGBLDIRUNDEF message (due to YDB@330a4e49)","shortMessageHtmlLink":"[YDB#999] Fix gtm_gbldir typo to gtmgbldir in ZGBLDIRUNDEF message (d…"}},{"before":"6daa892611c955a08ad1edd2ebfdcd4c948452c5","after":"4244c67b56f25d529b354b7e2f1faac4aa55c9ce","ref":"refs/heads/master","pushedAt":"2024-08-27T14:42:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#777] Fix r202/ydb777 subtest failure if M-profiling is randomly turned on\n\nBackground\n----------\n* The `r202/ydb777` subtest failed with the following diff once in a while.\n\n  ```diff\n  --- bool_expr_equnul-ydb777/bool_expr_equnul-ydb777.diff ---\n  420,424c420,424\n  < PASS: Test of [s x=$zlength(s)]\n  < PASS: Test of [s x=(s=\"\")]\n  < PASS: Test of [s x=(s'=\"\")]\n  < PASS: Test of [s:(s=\"\") x=1]\n  < PASS: Test of [s:(s'=\"\") x=1]\n  ---\n  > FAIL: [Actual=5729250893] more than [Maxlimit=3343200000] instructions\n  > FAIL: [Actual=5349247371] more than [Maxlimit=2870700000] instructions\n  > FAIL: [Actual=5349230464] more than [Maxlimit=2870700000] instructions\n  > FAIL: [Actual=5279236445] more than [Maxlimit=2796150000] instructions\n  > FAIL: [Actual=5329235199] more than [Maxlimit=2848650000] instructions\n  ```\n\nIssue\n-----\n* Testing showed that the failure happened when the random option was `MPROF:def`.\n\n* That is, when M-profiling is randomly turned on by the test framework (by setting\n  the `gtm_trace_gbl_name` env var to a non-empty value).\n\n* M-profiling adds a cost to each iteration of the for loop that gets executed (there\n  are 10 million iterations in the loop) and so the slowdown is expected.\n\nFix\n---\n* The fix is to disable that stage of the subtest if M-profiling is turned on and is\n  taken care of in this commit.","shortMessageHtmlLink":"[YDB#777] Fix r202/ydb777 subtest failure if M-profiling is randomly …"}},{"before":"3d0198124798aaf8942c06118b5558e301dca1ee","after":"6daa892611c955a08ad1edd2ebfdcd4c948452c5","ref":"refs/heads/master","pushedAt":"2024-08-23T14:26:00.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#963] [V7.0-005] [GTM-F135418] New v70005/extend_restr_zlink-gtmf135418 subtest of extending restriction facility to ZLINK, ZRUPDATE & SET $ZROUTINES\n\nRelease note (http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V7.0-005_Release_Notes.html#GTM-F135418) says:\n\n> The GT.M restrictions facility recognizes ZLINK, ZRUPDATE and\n> SET \\$ZROUTINES. When an explicit ZLINK (not auto-zlink),\n> ZRUPDATE, or SET \\$ZROUTINES restriction conditions are\n> configured, the restricted command issues a RESTRICTEDOP error\n> message. Previously, the restrictions facility did not support\n> ZLINK, ZRUPDATE, or SET \\$ZROUTINES. (GTM-F135418)","shortMessageHtmlLink":"[YDB#963] [V7.0-005] [GTM-F135418] New v70005/extend_restr_zlink-gtmf…"}},{"before":"d7ac844b948df5114880aebfc28249c48381c060","after":"3d0198124798aaf8942c06118b5558e301dca1ee","ref":"refs/heads/master","pushedAt":"2024-08-20T15:29:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#999] Fix gde/gdeput and v43001/zgbldir subtests to test new ZGBLDIRUNDEF error and SET $ZGBLDIR=\"\" behavior\n\nBelow changes are due to new YDB behavior (YDB@cb60a085).\n\n* The `gde/gdeput` subtest needed changes as the case when `gtmgbldir` is undefined now issues\n  a `ZGBLDIRUNDEF` error. This meant 3 subtest cases corresponding to when `gtmdbldir` is undefined\n  were merged into a single `Case 1`.\n\n  3 other subtest cases corresponding to when `gtmgbldir` is defined were left as is.\n\n  Overall, the test script `gde/u_inref/gdeput.csh` was reworked to make it easier to understand\n  the test flow and output. This also meant corresponding enhancements to `gde/outref/gdeput.txt`.\n\n* The `v43001/zgbldir` subtest reference file needed change because `$zgbldir` now shows up as the\n  empty string (i.e. `\"\"`) when\n  - `gtmgbldir` env var is undefined OR\n  - when a `set $zgbldir=\"\"` is done.","shortMessageHtmlLink":"[YDB#999] Fix gde/gdeput and v43001/zgbldir subtests to test new ZGBL…"}},{"before":"e8a935be4e8574107b7993949cf7f57054c232f5","after":"d7ac844b948df5114880aebfc28249c48381c060","ref":"refs/heads/master","pushedAt":"2024-08-19T15:25:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"Fix setting $notmygroup variable in some audit-related tests to work correctly if the user is root\n\nBackground\n----------\n\nAudit related tests requires a group name which the actual user belongs to, usually stored in variable `$mygid`, and another group ID, which the user does not belong to, usually stored in variable `$notmygid`. This is done by selecting first group from `/etc/group`, which is usually the `root` group, regular users are not member of it:\n\n```\nset notmygid=`cat /etc/group | head -n1 | cut -d':' -f1`\n```\n\nIssue\n-----\n\n[As this comment points out](https://gitlab.com/YottaDB/DB/YDBTest/-/merge_requests/2067#note_2049738300 \"[YDB#963] [V7.0-005] [GTM-F135418] New v70005/extend_restr_zlink-gtmf135418 subtest of extending restriction facility to ZLINK, ZRUPDATE & SET $ZROUTINES\"), tests may run as `root` user, which is member of the `root` group, so selecting it as _not-my-group_ can be wrong.\n\nFix\n---\n\nAs [the comment suggests](https://gitlab.com/YottaDB/DB/YDBTest/-/merge_requests/2067#note_2049738300 \"[YDB#963] [V7.0-005] [GTM-F135418] New v70005/extend_restr_zlink-gtmf135418 subtest of extending restriction facility to ZLINK, ZRUPDATE & SET $ZROUTINES\"), exclude self group from `/etc/group` file when picking a group name from it:\n\n```\nset mygid=`id -gn`\nset notmygid=`cat /etc/group | grep -vw $mygid | head -n1 | cut -d':' -f1`\n```","shortMessageHtmlLink":"Fix setting $notmygroup variable in some audit-related tests to work …"}},{"before":"6e83ed6afb2ac08e3f0d8d7b0855eea224d26007","after":"e8a935be4e8574107b7993949cf7f57054c232f5","ref":"refs/heads/master","pushedAt":"2024-08-19T14:12:42.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nars1","name":"Narayanan Iyer","path":"/nars1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/28790583?s=80&v=4"},"commit":{"message":"[YDB#959] New r202/jnlswitch_set_perf-ydb959 subtest to verify no global SET performance loss during jnl file switch","shortMessageHtmlLink":"[YDB#959] New r202/jnlswitch_set_perf-ydb959 subtest to verify no glo…"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEuycyuQA","startCursor":null,"endCursor":null}},"title":"Activity · YottaDB/YDBTest"}