Key: | Active | Review | Fixed | Tested | Deferred | Closed |
# | mtime | type | status | subsystem | title |
---|---|---|---|---|---|
comments | |||||
b1c37f9e55 | 2024-10-12 08:51:23 | Code_Defect | Open | The waitons table in testconfig is not working correctly. Items start before upstream items are competed. | |
b953a528e0 | 2024-10-09 15:36:53 | Code_Defect | Open | mt_runstep script does not set the log file | |
acb37571e8 | 2024-08-16 02:17:32 | Code_Defect | Open | changes seen in 13eeb commit not in v1.65. May or may not be an issue | |
ca7a0d33ce | 2024-03-28 22:39:31 | Code_Defect | Open | Megatest dboard process taking 100% for 400+ hours | |
Megatest dboard process taking 100% for 400+ hours It happens to multiple users and hosts | |||||
9e8bc27fe3 | 2024-03-25 21:30:51 | Code_Defect | Open | Order of columns is not consistent in Dashboard Run Summary tab | |
Even if there are dependencies, I believe columns in the dashboard Run Summary should be listed in the same order. They are randomly different for different runs, each time they are displayed. The difference makes visual comparison difficult. Just want to know if the column order can be deterministic. | |||||
6d871cd4cc | 2024-03-25 21:24:40 | Code_Defect | Open | remove-keep not honoring testpatt | |
If I run: megatest -remove-keep 1 -target %/% -runname % -testpatt init,exec -status FAIL -actions print,remove-runs -age 1h -precmd echo I get: 1227/all: megatest -remove-runs -target 1227/all -runname 22025.0621 -testpatt % Skipping handling of 1227/all/22025.0641 as it is younger than 1h Skipping handling of 1227/all/22025.0701 as it is younger than 1h Unless the remove-keep is only matching targets where init/exec have status=FAIL this seems like a bug. | |||||
b68c9de2d6 | 2024-03-25 19:53:46 | Code_Defect | Open | Megatest dashboard should respect TESTPATT order for tests | |
In the dashboard runs tab, please order the tests in TESTPATT order. | |||||
4a150c7bf2 | 2024-03-25 18:42:20 | Code_Defect | Open | Megatest not running system calls from global.runconfig.post when defined as wildcard | |
Megatest is not running system calls which are defined inside wildcard target definitions in global.runconfig.post. Workaround already provided by Env team. The system calls work fine when defined as defaults or in completely defined target. Files with information: /nfs/site/disks/ch_icf_megatest_001/scheema/megatestqa/esdcollqa/configs/global.runconfigs.post /nfs/site/disks/ch_icf_megatest_001/scheema/megatestqa/esdcollqa/configs/global.runconfigs.config Saad. | |||||
9506c87ca5 | 2024-02-04 17:00:36 | Code_Defect | Open | dashboard crashes in chained-waiton. | |
d18665ecd9 | 2024-01-23 21:46:51 | Code_Defect | Open | testconfig evaluation leaking to other tests. | |
ae9b88b9ac | 2023-12-15 16:52:47 | Code_Defect | Open | crash in remove-runs on highly loaded machine, need exception handler? | |
ddecbfdf1d | 2023-02-22 19:50:57 | Code_Defect | Open | Test recovery doesn't seem to be working right | |
71bc1fd416 | 2023-01-17 19:41:06 | Code_Defect | Open | Shell and scheme are evaluated in comments. This is not proving useful. Please disable. | |
2223f4fd04 | 2022-12-13 18:22:58 | Code_Defect | Open | line ending in \ not working in scripts and # breaks scripts in testconfig | |
cd7bd96b45 | 2022-12-08 00:06:59 | Code_Defect | Open | variable leakage between tests when using pre-launch-env-vars and include | |
9004c56d24 | 2022-10-13 21:52:34 | Code_Defect | Open | runconfigs should be read only once | |
From Robert: There is a real issue with the time it takes megatest to process runconfigs. Every #{shell ...} command is processed in every target from every included file even if the target is not the one being run, or a simple -list-targets is given on the command line. To make matters worse, when running a regression, not only does the main megatest "mtest" call processes runconfigs, so does any server started by the regression run. And if it takes a LONG time to process the runconfigs, the regression run will spend a lot of time waiting for the server to start. Every single call to megatest, whether its to start the regression, or start a server, or whatever, is subject to the time it takes to process the runconfig files. The parsing of runconfigs should happen 1 time per session, and the evaluation of value should only happen 1 time and when its needed/used (there should not be a global evaluation of all parameters across all targets unless there is some kind of dump operation occurring). While I appreciate that there was some original reason/intent for re-parsing the runconfigs the entire process is leading to a substantial performance issues in regression runs. Even if there is a need to re-evaluate a variable value, there should be a means of indicating so, like: VAR #{eval ...} Something needs to be done to improve performance of reading the runconfigs. | |||||
21ff1c38b2 | 2022-08-02 15:19:11 | Code_Defect | Open | Starting from clean (no cache in /tmp) the main.db is not always copied | |
028d5ebf87 | 2022-07-18 15:44:48 | Code_Defect | Open | Too many open files | |
2c61853004 | 2022-07-07 20:55:41 | Code_Defect | Open | incorrect behavior with rerun-all | |
5b2cffd17c | 2022-06-22 21:35:36 | Code_Defect | Open | Variables in one target with no value produce "<var>=" in another target's test's env | |
When a variable is defined in a target earlier in the runconfig file, with no value, like MYENVVAR it appears with the name "MYENVVAR=" in the environment of a test run from a later target in the runconfig. It does not appear when doing megatest -show-runconfig -target <target> The workaround is to put "" for the value of the var. | |||||
a5ae5422ab | 2022-06-16 15:45:29 | Code_Defect | Open | trailing space in config section prevents recognition and is hard to detect | |
9243f53c6d | 2022-06-02 02:24:24 | Code_Defect | Open | access to remote-conndat needs to be protected against not-yet-set remote. | |
4e12dfbc1b | 2022-05-22 02:06:10 | Code_Defect | Open | Switch default to no local db access | |
73e3742297 | 2022-05-21 01:35:20 | Code_Defect | Open | current defaults for free disk space are based on some crazy large corporate needs. | |
c58f15f80d | 2022-05-20 21:26:06 | Code_Defect | Open | The message "looking for zombie" is too frequent and or needs context. | |
590e7b7930 | 2022-05-04 20:50:29 | Code_Defect | Open | when step crashes logpro rules do not get applied. | |
23bdcb1c3e | 2022-04-20 22:28:27 | Code_Defect | Open | remove-runs removed non-matching extra runs | |
65bfe02932 | 2022-03-25 20:55:39 | Code_Defect | Open | Megatest not executing some parts of a test | |
For tests that have a step which is 2 commands joined with an && it's causing problems. The workaround for now is to split the command into two steps. | |||||
354935ae2b | 2022-03-25 18:47:51 | Code_Defect | Open | runtime limit assigned in runconfigs not being honored | |
Seeing instances of batch jobs running megatest far exceeding the runtime limit that is in the config. A couple of possible causes: megatest kills the job but the batch system doesn't detect that it's dead megatest does not honor the limit the limit could be getting overriden somewhere else that we're not seeing | |||||
2102f85b7e | 2021-07-08 18:26:23 | Code_Defect | Open | typo in any testconfig affects top level environment | |
If a test in the test list for a run has a typo like "items]" instead of "[items]" (missing bracket) it causes an env check to fail at the top level (precheck test) megatest.csh will contain "#setenv items]", and precheck will flag an illegal env var. | |||||
fbfdb653fd | 2021-03-19 18:03:44 | Code_Defect | Open | v1.65/83 with only one disk0 entry does horrible things ... | |
ee2c833eaf | 2021-02-19 19:16:39 | Code_Defect | Open | crash on start dashboard | |
9644eb4ca3 | 2020-10-30 14:30:32 | Code_Defect | Open | crash in server.log | |
86662a0273 | 2020-10-08 20:21:59 | Code_Defect | Open | Crash | |
96a9e539f8 | 2020-10-07 04:53:24 | Code_Defect | Open | Crash | |
04e5164c68 | 2020-09-23 22:40:45 | Code_Defect | Open | Crash | |
e7596943a5 | 2020-09-23 22:04:47 | Code_Defect | Open | spurious readonly database crash. | |
adf67e869a | 2020-09-23 19:14:09 | Code_Defect | Open | Crash | |
57fd79cf36 | 2020-06-04 16:43:41 | Code_Defect | Open | fix run removal if targets have been removed | |
If the target has been removed from the runconfig, the run does not show up in dashboard, and cannot be removed using the dashboard. | |||||
677155e2a6 | 2020-04-24 22:02:10 | Code_Defect | Open | With no runconfig Megatest can crash - on no file need to return empty hash, not #f | |
5d87c510e8 | 2019-10-22 17:48:37 | Code_Defect | Open | Area to area run inheritance | |
c4f251d133 | 2019-10-22 16:12:29 | Code_Defect | Open | megatest -list-runs % -fields run:target,runname+tests:testname,item_path incorrectly lists steps | |
c2bd3c6dac | 2019-09-13 17:37:43 | Code_Defect | Open | Subruns launched as -rerun-clean get stuck. | |
07469a3053 | 2019-09-12 22:49:20 | Code_Defect | Open | subrun requires runwait -> give an error is run-wait specified | |
276ad8c9cf | 2019-09-05 22:48:36 | Code_Defect | Open | Need to add ext-tests/mt_vars to the testsuite and fix the MT_TARGET not set issue. | |
fabb7405f5 | 2018-11-08 17:35:40 | Code_Defect | Open | Variables starting with ! leaking into environment when variable is set for a totally open regex | |
When a user puts a !FOO variable into an include in the runconfig that matches everything, like /.*/, it appears to match default as well, and when that happens, those variables leak into the environment. | |||||
e2b83cfeaf | 2018-09-04 19:54:06 | Code_Defect | Open | toplevel test does not fire when dependent on a failed itemized test and not using -run-wait | |
../ | |||||
13680e7907 | 2018-08-10 17:39:44 | Code_Defect | Open | Goodtests not starting due to no propagation of PREQ_FAIL | |
d9c4f6e711 | 2018-05-22 23:30:56 | Code_Defect | Open | broken wildcard target value binding when value uses [system #{getenv ... | |
Example problem: from runconfigs.config: [full] ... /.*/ THINGS_LIST [system #{getenv THING_ORACLE_EXE} listem] OKSTUFF hello % megatest -showrunconfig THINGS_LIST expected_value OKSTUFF hello % megatest -showrunconfig -target full OKSTUFF hello **THINGS_LIST does not appear** | |||||
8b11992f91 | 2017-12-06 21:43:21 | Code_Defect | Open | Need protection against bad hosts in lowestload list. Exponential backoff if there is a timeout or very high load. | |
24c8995e89 | 2017-11-29 23:50:39 | Code_Defect | Open | Run control panel has undefined targets for version 1.65/04 | |
All the target definitions have "runs" in the run tree browser. | |||||
2bf349ad96 | 2017-09-06 17:42:11 | Code_Defect | Open | selecting edit testconfig from the context menu in run tab launches vi even though my EDITOR env var is "emacs" | |
827909e4da | 2017-09-05 23:21:49 | Code_Defect | Open | dashboard running on non-homehost with large db can hang | |
I have observed that if you are running dashboard on a non-homehost it will work until the database size reaches some threshold, at which point it will freeze. When restarting, it immediately freezes. I suspect the database size is the critical dimension -- syncing likely takes longer than the action loop in dashboard. In the instance I see it, the megatest.db size is 5.4M with 4k tests and 11 runs. Running dashboard on homehost, there is no issue at all and dashboard responds very quickly. Here is the console log from dashboard when we see the freezing issue: Checking for user runconfigs config ... WARNING lefkowit.runconfigs.config file ...doesn't exist do this if you care ### Add custom targets/overrides to global targets here to ./configs/lefkowit.runconfigs.config Checking for required/common linktree path: /p/fdk/gwa/lefkowit/qa/libanaacatqa/links ... exists /p/fdk/gwa/lefkowit/qa/libanaacatqa/links Defined disks: ------------------------------------ exists /p/fdk/gwa/lefkowit/qa/libanaacatqa/runs ------------------------------------ Checking if megatest variables are already defined ... STARTING DASHBOARD ... WARNING: Current policy requires running dashboard on homehost: (10.38.45.46 . #f) INFO: Trying to start server (megatest -server 10.38.45.46 -m testsuite:libanaacatqa) ... INFO: (0) Starting server on 10.38.45.46, logfile is /nfs/pdx/disks/ch_icf_megatest_001/lefkowit/mtTesting/megatestqa/libanaacatqa/logs/server.log #====================================================================== # NBFAKE logging command to: /nfs/pdx/disks/ch_icf_megatest_001/lefkowit/mtTesting/megatestqa/libanaacatqa/logs/server.log # megatest -server 10.38.45.46 -m testsuite:libanaacatqa #====================================================================== WARNING: problem with directory /p/fdk/gwa/lefkowit/fossil/ext/acatqa_ext/trunk/tests, dropping it from tests path WARNING: problem with directory /nfs/pdx/disks/ch_icf_megatest_001/lefkowit/mtTesting/megatestqa/relqa/tests, dropping it from tests path WARNING: problem with directory /nfs/pdx/disks/ch_icf_megatest_001/lefkowit/mtTesting/megatestqa/libanaacatqa/tests, dropping it from tests path NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 1000 to 2000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 2000 to 4000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 4000 to 8000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 8000 to 16000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 16000 to 32000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 32000 to 64000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 64000 to 128000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 128000 to 256000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 256000 to 512000 ... NOTE: increasing poll interval from 1125899906842624000 to 2251799813685248000 NOTE: updates are taking a long time, 3.0s elapsed. NOTE: increasing poll interval from 2251799813685248000 to 4503599627370496000 NOTE: updates are taking a long time, 3.0s elapsed. Call history: db.scm:1972: call-with-current-continuation db.scm:1972: with-exception-handler db.scm:1972: ##sys#call-with-values db.scm:1972: k3436 db.scm:1972: g3440 dashboard.scm:795: current-seconds dashboard.scm:798: dboard:tabdat-allruns-by-id dashboard.scm:798: hash-table-set! dashboard.scm:803: debug:print common_records.scm:131: debug:debug-mode common_records.scm:132: with-output-to-port dashboard.scm:804: iup-base#attribute dashboard.scm:805: floor dashboard.scm:3551: k7615 dashboard.scm:3551: g7619 dashboard.scm:3551: print-call-chain <-- inexact number cannot be represented as an exact number Callback error in dashboard:runs-tab-updater Full condition info: ((exn (location inexact->exact) (call-chain (#(db.scm:1978: loop #f #f) #(db.scm:1978: loop #f #f) #(db.scm:1978: loop #f #f) #(db.scm:1972: call-with-current-continuation #f #f) #(db.scm:1972: with-exception-handler #f #f) #(db.scm: 1972: ##sys#call-with-values #f #f) #(db.scm:1972: k3436 #f #f) #(db.scm:1972: g3440 #f #f) #(dashboard.scm:795: current-seconds #f #f) #(dashboard.scm:798: dboard:tabdat-allruns-by-id #f #f) #(dashboard.scm:798: hash-table-set! #f # f) #(dashboard.scm:803: debug:print #f #f) #(common_records.scm:131: debug:debug-mode #f #f) #(common_records.scm:132: with-output-to-port #f #f) #(dashboard.scm:804: iup-base#attribute #f #f) #(dashboard.scm:805: floor #f #f))) (arg uments (9.00719925474099e+18)) (message inexact number cannot be represented as an exact number)) (type)) NOTE: updates are taking a long time, 3.0s elapsed. <stack dump repeats regularly, probably in the dashboard event loop> | |||||
be73f72774 | 2017-08-24 17:41:16 | Code_Defect | Open | lt link in MT_RUN_AREA_HOME needs to be recreated if linktree changes | |
If linktree is changed in megatest.config, lt link in MT_RUN_AREA_HOME should be updated to match. | |||||
311d767396 | 2017-07-17 15:01:42 | Code_Defect | Open | Running list runs in tests directory causes crash | |
8c972842e9 | 2017-06-28 03:41:39 | Code_Defect | Open | a test which results in "zero items" state/status will cause runner process to stop, even though tests which may run and are not dependent on this zero items test are ready to run. they are left dangling. | |
6cae932a9d | 2017-06-25 05:11:14 | Code_Defect | Open | make NUMTESTS=30 bigrun3 RUNNAME=stress_test003 in tests/fdktestqa/testqa never finishes. | |
e27c06a338 | 2017-06-22 02:16:11 | Code_Defect | Open | Crash on migration of target to new target pattern | |
88707d778c | 2017-06-01 04:39:53 | Code_Defect | Open | Inconsistent naming of server log files, sometimes includes pid, sometimes not | |
855c60b695 | 2017-05-30 22:29:22 | Code_Defect | Open | freeze column width of matrix widget in run summary tab | |
In an active run, the run summary matrix view induces headaches in yours truly. The column widths vary wildly from one second to the next. Eg: on second, the column fits width of "REMOTEHOSTSTART" and the next fits "PASS". multiply this delta by # of tests. | |||||
12dfb44595 | 2017-05-30 22:23:17 | Code_Defect | Open | add timestamp to items in server logs | |
motivation - it is hard to debug when a server has gone wrong. this is a feature indented for analysts and developers. | |||||
c21083ffba | 2017-05-30 22:21:03 | Code_Defect | Open | client abort when server version does not match | |
current behavior when client version does not match server version is for client to launch another server. net result is a darwinian struggle of multiple version variants of megatest server. | |||||
944da29a23 | 2017-04-24 22:42:09 | Code_Defect | Open | in run tab: state filter + status filter result in wrong result | |
SETUP: 0) setup megatest build from tag v1.6407) 1) under megatest folder, create ext-tests. Poplulate subdir from megatest_qa fossil using commit d3e9c96dc307d7c941ea973d524adb4b267cbd56 (currently tip at time of writing) 2) Using megatest_qa testsuite, perform two runs, say named "run1" and "run2". run1 completes first. All tests in both runs should resolve to COMPLETED/PASS. 3) In run1, manually set tconfdisks/tom/n to RUNNING/PASS 5) in run1, manually set tconfdisks/fred/d to RUNNING/FAIL 6) in run1, manually set tconfdisks/bob/p to COMPLETED/FAIL 7) Make sure "HIDE" mode is selected for filters. 8) select state filter "RUNNING" 9) select status filter "FAIL" OBSERVE: two columns a. run2 having tconfdisks topeleven and items tom/n and fred/d items as "RUNNING" b. run1 having tconfdisks toplevel and items tom/n and fred/d as "RUNNING" c. run1 having tconfdisks item bob/p "FAIL". ISSUE: item a above is unexpected, since they are in fact COMPLETED/PASS in the database. item b and c are expected and correct. | |||||
6606a69c0a | 2017-04-24 22:25:48 | Code_Defect | Open | Megatest status rollup for test with items | |
If a test has items, requesting update to the state/status of the top-level test to roll up. | |||||
514327decf | 2017-04-21 00:00:45 | Code_Defect | Open | "misc" "default" and "%: appear in hierarchy widget of Run Control panel. THey shoulod not | |
Since default and misc and % expand to non-sensical values and are not valid targets for runs, we do not expect to see these as selectable targets in run control panel. | |||||
9f9c407694 | 2017-04-20 22:42:18 | Code_Defect | Open | Please enable section creation to be effective without any variables in config files | |
622b1b6a0e | 2017-04-04 00:05:24 | Code_Defect | Open | when removing runs, stack dump at end of (long) log | |
Following from xterm popped up from deleting runname 164am: (accessed by right clicking on a test in this run on dashboard->run->clean complete run INFO: (1) Recursively removing /nfs/pdx/disks/icf_env_disk001/bjbarcla/gwa/issues/mtdev/randy-slow/reproduce/qa/libanabeqa/links/p1275/2/PDK_r2.0/libana/164am/oalib_propbag_diff Error: (directory) cannot open directory - No such file or directory: "/nfs/pdx/disks/icf_env_disk001/bjbarcla/gwa/issues/mtdev/randy-slow/reproduce/qa/libanabeqa/links/p1275/2/PDK _r2.0/libana/164am/oalib_propbag_diff" Call history: common_records.scm:224: debug:debug-mode common_records.scm:225: port? common_records.scm:225: with-output-to-port runs.scm:1903: file-exists? runs.scm:1905: debug:print-info common_records.scm:224: debug:debug-mode common_records.scm:225: port? common_records.scm:225: with-output-to-port runs.scm:1906: file-exists? runs.scm:1907: runs:safe-delete-test-dir runs.scm:1662: directory-utils#directory-fold directory-utils.scm:128: ##sys#get-keyword directory-utils.scm:130: type-checks#check-procedure directory-utils.scm:132: check-directory directory-utils.scm:79: directory? directory-utils.scm:132: directory <-- | |||||
7b698cdf7b | 2017-03-10 22:14:44 | Code_Defect | Open | mtutil run crashes | |
mtutil run -area ext-tests -target a/b/c/d Error: (null-list?) bad argument type - not a list: #<hash-table (2)> Call history: configf.scm:50: hash-table-ref/default configf.scm:49: config:assoc-safe-add configf.scm:41: ##sys#get-keyword configf.scm:42: filter configf.scm:43: append configf.scm:48: hash-table-set! mtut.scm:843: configf:lookup configf.scm:416: hash-table? configf.scm:417: hash-table-ref/default mtut.scm:844: string-split mtut.scm:845: hash-table-copy mtut.scm:841: ##sys#call-with-values mtut.scm:852: command-line->pkt mtut.scm:392: current-seconds mtut.scm:397: current-user-name mtut.scm:410: filter <-- | |||||
0331ed63d5 | 2017-02-28 21:54:18 | Code_Defect | Open | megatest -v returns stack dump after showing help. Expect no stack dump. | |
54821b6db6 | 2017-02-10 00:59:36 | Code_Defect | Open | "make PREFIX=/some/where" install only installs megatest binary (and not, for example, dashboard) | |
77d284a3e8 | 2017-02-03 01:01:34 | Code_Defect | Open | on test control panel, changing state to "waived" does not work | |
changing status from fail to pass works changing status from fail to waived brings up the waive dialog, but on "apply and close" click, the message "Error: in callback: unbound variable: rmt:test-set-state-status-by" appears on the console, and dialog does not close. status does not change. | |||||
7cb1419578 | 2017-02-03 00:57:53 | Code_Defect | Open | run tab - cannot resize columns. runnames and targets of long length cannot be distinguished | |
In the run tab, the width of matrix columns for runs is fixed. If a field value for the target or the run name spans more than ~14 characters, it is cut off. This could be worked around in v1.60/29 by stretching the entire window horizontally by dragging the right corner out. Since the matrix was bound to the right side, the column widths would scale out. In current version (1.63/05) the matrix is not bound to the left edge, so stretching has no effect. Marking Severe; reported by end user. | |||||
fe82fa6b60 | 2017-02-03 00:57:11 | Code_Defect | Open | dashboard font missing underscores (_) or widget too small and cuts it off... | |
In Run tab, when viewing test names on leftmost column, the test names look like they have blank spaces where one would expect underscores. This was not the case in 1.60/29 (marking severe - reported by two users) | |||||
bc11edad89 | 2017-02-02 20:34:21 | Code_Defect | Open | add -state and -status to -find-files | |
78b26c37f3 | 2017-01-13 18:52:17 | Code_Defect | Open | Dashboard hangs when core count is 32 or 64 | |
For example, plxcm7003. Hang occurs when switching to dashboard "run" or "run summary" tab | |||||
61054a5780 | 2016-09-13 15:24:04 | Code_Defect | Open | dashboard sort by test name is not sorting by test name | |
The sort +testname and -testname in dashboard are not sorting testname alphabetically - this should take the itempath into account if it exists. | |||||
0954ef0fbc | 2016-09-02 19:51:52 | Code_Defect | Open | megatest -list-targets error when no write access to MT_RUN_AREAHOME | |
In megatest 1.6104 -list-targets attempts to create a symlink, so cannot check targets in another user's area. NEEDS A TEST? | |||||
3c090ef0ad | 2016-08-31 18:10:11 | Code_Defect | Open | megatest commands require iup/DISPLAY | |
Non-dashboard megatest commands are requiring DISPLAY to be set | |||||
0bdc2f3f8f | 2016-08-30 15:34:09 | Code_Defect | Open | refdb: set does not create sxml files if refdb dir is new | |
creating a new refdb with "refdb set" does not create the required sxml files to be able to open the new refdb via "refdb edit" | |||||
8179e10483 | 2016-08-30 15:32:57 | Code_Defect | Open | refdb: set appends changes but does not replace | |
refdb set command does not replace existing lines in the .dat file when updating existing keys: refdb set db row col data [] [col] row data ... refdb set db row col data [] [col] row data row data | |||||
5a2549bc82 | 2016-08-26 19:59:37 | Code_Defect | Open | Remove support for db and monitor directory control and improve lt support. | |
09f81a879a | 2016-08-04 23:29:54 | Code_Defect | Open | Run Summary tab: Need to toggle run selection 3 times to see main pane update to new run | |
When having multiple runs, when I launch a new run, I click on the new run name that appears on the left pane of the Run Summary tab. The pain pane still shows results for the run that was previously selected. If I reselect the prior run, then select the new run again, it updates properly. | |||||
503763b420 | 2016-08-02 21:55:34 | Code_Defect | Open | #{get foo} => fails ungracefully (needs message for missing param) | |
a926703df5 | 2016-08-01 21:03:05 | Code_Defect | Open | ezstep exiting 6 transitions status to "FAIL". Expectation is a transition to status "SKIP" | |
in my testconfig, I have a step which runs a script having the code "exit 6" In the test control panel, the Steps table correctly reflects Status=6 for the step. However, the overall status is "FAIL". I expected "SKIP". | |||||
aa2b3ffab0 | 2016-06-22 20:57:12 | Code_Defect | Open | dashboard crashes when clicking on "Run Details" tab | |
Warning (#<thread: Main loop>): in thread: call of non-procedure: #f Call history: dashboard.scm:1853: file-modification-time dashboard.scm:1853: file-modification-time dashboard.scm:1853: file-modification-time dashboard.scm:1853: file-modification-time dashboard.scm:1853: file-modification-time dashboard.scm:1846: k3511 dashboard.scm:1846: g3515 dashboard.scm:1858: file-exists? dashboard.scm:1859: file-modification-time dashboard.scm:1861: current-seconds dashboard.scm:1862: d:alldat-please-update dashboard.scm:1862: d:alldat-last-db-update dashboard.scm:1862: dashboard:recalc dashboard.scm:1863: d:alldat-curr-tab-num dashboard.scm:1871: d:alldat-curr-tab-num dashboard.scm:1889: dashboard:update-new-view-tab <-- Error: uncaught exception: #<condition: (exn type)> [6] Exit 70 dashboard -rows 25 | |||||
3699db2b31 | 2016-06-21 23:07:42 | Code_Defect | Open | test vacuously "PASS"es if missing ezsteps / setup section | |
When a testconfig is missing a specification of things to run, eg in [ezsetps] section, the test passes. II would expect the test to fail since its specification is incomplete. IIn my case, the error was a typo in spelling "ezsteps", but the test passed whereas it should have failed since the underlying step was actually failing but was masked by this issue. | |||||
8ea9b6e119 | 2016-05-12 04:45:47 | Code_Defect | Open | deadlock and mutex failure | |
d5640a8cc1 | 2016-05-09 04:53:20 | Code_Defect | Open | Finish launch:recover-test or refactor launch:execute to support running with no master mtest process | |
ed4b1d7221 | 2016-05-09 03:54:11 | Code_Defect | Open | -run should output test results as they complete and a summary on completion of the run | |
4a26d0d54d | 2016-02-05 16:57:54 | Code_Defect | Open | Run data disappears from dashboard | |
Run data intermittently disappears from the megatest dashboard. It can be recovered by closing the dashboard and reopening it, but "Refresh" does nothing. | |||||
3c7ceb7107 | 2016-01-29 17:30:19 | Code_Defect | Open | Megatest dashboard hides some tests when number of tests is large | |
When I expand a test with many subtests (200), if I use the scrollbar to scroll to the bottom, some tests still do not show up. This is intermittent. Sometimes if I scroll to the top and then back down, it then shows all tests; other times I cannot see the additional tests at all. | |||||
7abe077381 | 2015-12-01 18:31:01 | Code_Defect | Open | dashboard crashes after 5-10 mins | |
Its the central run dir. Pls let me know if you need more info. Warning (#<thread: Main loop>): in thread: (finalize!) database is locked: #<sqlite3:statement sql="(5�"> Call history: db.scm:3181: thread-sleep! db.scm:3182: db:delay-if-busy db.scm:3165: ##sys#get-keyword db.scm:3166: configf:lookup configf.scm:288: hash-table? configf.scm:289: hash-table-ref/default db.scm:3169: db:dbdat-get-path db.scm:3170: db:dbdat-get-db db.scm:3171: conc db.scm:3172: call-with-current-continuation db.scm:3172: with-exception-handler db.scm:3172: ##sys#call-with-values db.scm:3178: file-exists? db.scm:3172: k3877 db.scm:3172: g3881 db.scm:2039: sqlite3#for-each-row <-- Error: uncaught exception: #<condition: (exn sqlite3)> | |||||
342a2ed62f | 2015-10-21 20:50:43 | Code_Defect | Open | megatest -list-runs does not filter on state/status | |
megatest -list-runs % -state COMPLETED -status FAIL,CHECK does not filter on state/status | |||||
2a890be4f1 | 2015-09-24 00:06:34 | Code_Defect | Open | Have observed that hooks fire twice | |
de737b7f90 | 2015-09-10 17:45:12 | Code_Defect | Open | megatest not honoring hard coded launcher | |
b535d2274f | 2015-09-08 15:28:49 | Code_Defect | Open | items not applied across multiple waitons | |
With multiple waiton dependencies, the items are applied only to the last waiton dep. | |||||
a706ae9e4f | 2015-08-28 15:57:14 | Code_Defect | Open | Itemmap handling of % | |
When using itemmap and mode itemwait, if the mapped item contains a '%' the itemwait is behaving like toplevel - it is not starting the item when its dependencies have been met. Example, TESTA (waiton TESTB, mode itemwait) ITEM1/fluff ITEM2/fluff TESTB repo/ITEM1 repo/ITEM2 If I use itemmap to convert ITEM1/fluff to %/ITEM1, TESTA/ITEM1/fluff does not start until all items in TESTB are complete. | |||||
3c517427a3 | 2015-08-28 15:53:05 | Code_Defect | Open | Tests with items rolling up to UNKNOWN state | |
Tests with items are rolling up to UNKNOWN state rather than PASS/FAIL/WARN as applicable. This is happening with any number of items - I've tried 1 and 15. | |||||
3c3a1b98a2 | 2015-08-20 14:23:45 | Code_Defect | Open | Incorrect behavior of section/-var in -show-runconfig | |
49481ee087 | 2015-08-05 00:13:44 | Code_Defect | Open | Ensure MT_TEST_NAME and MT_ITEM_PATH are visible in testconfig processing | |
eddf860353 | 2015-06-24 20:16:22 | Code_Defect | Open | Dashboard collapse option with first-rime user | |
I was helping a new user get set up today and I think we hit a first-use behavior in the dashboard. The behavior we noticed is that tests with test items start as expanded, which is fine. I had him select the collapse button and the test in progress collapsed. But as each successive test was populated with test items, that new test was presented as expanded. It appears that if there is nothing to collapse in a test and there is no previous regression using the test, the collapse is not applied. | |||||
b68e393028 | 2015-06-14 03:48:26 | Code_Defect | Open | test2 is not detecting that it can end. | |
41bbd050d0 | 2015-04-30 16:56:12 | Code_Defect | Open | server stuck issue - user can't work until cleanup-db is run | |
6a4329c9c6 | 2015-04-02 04:28:32 | Code_Defect | Open | removing tests using state/status FAIL where some items are FAIL and some are PASS also removes PASS items | |
That is a tough one. It seems it could be considered a bug in Megatest. I’m treating a toplevel test in the same way as I’m treating items and non-itemized tests. What I need to do is not apply the remove to the FAIL toplevel if there are any non-fail items. This will be a bit tough and I’d like to wait until 1.60 to fix it. | |||||
beea22d42a | 2015-04-02 04:18:10 | Code_Defect | Open | Improve deletion of tests | |
61e921f9cf | 2015-04-02 03:53:09 | Code_Defect | Open | kill tests not working well under high NFS load | |
410ccd8f36 | 2014-09-24 22:52:41 | Code_Defect | Open | crash in dashboard when no tests in tests dir. | |
3599e71a11 | 2014-05-09 22:47:29 | Code_Defect | Open | Runs with failed tests showing as running | |
Runs with failed tests showing as running when a test launches a new megatest instance. | |||||
0b723d1367 | 2014-03-17 03:49:10 | Code_Defect | Open | (print (rmt:test-get-records-for-index-file 1 "test1")) => unspecified | |
INFO: (1) Test exited in state=RUNNING, setting state/status based on exit code of #t and rollup-status of 127 Error: (for-each) bad argument type - not a list: #<unspecified> Call history: http-transport.scm:274: thread-terminate! http-transport.scm:275: debug:print-info common_records.scm:68: debug:debug-mode http-transport.scm:225: k682 http-transport.scm:225: g686 rmt.scm:59: db:string->obj db.scm:1749: regex#regexp db.scm:1748: regex#string-substitute db.scm:1747: base64#base64-decode db.scm:1746: with-input-from-string db.scm:1750: s11n#deserialize tests.scm:331: with-output-to-port tests.scm:334: conc <-- Obtained lock for megatest-rollup-sqlitespeed.html | |||||
2661ce8c0f | 2014-02-26 23:56:02 | Code_Defect | Open | uncaught exception on pass/fail roll up for items | |
Obtained lock for megatest-rollup-pycell_xor.html ... stuff ... Error: uncaught exception: #<condition: (join-timeout-exception)> | |||||
48c7b2d605 | 2014-02-24 05:36:48 | Code_Defect | Open | crash in single test | |
[0] http-transport:client-connect -> ("192.168.0.35" 8080 #<request> #<request>) pid:1559 INFO: (1) Running -runstep, first change to directory /mfs/matt/data/megatest-inmem-with-per-run/tests/fullrun/tmp/mt_links/ubuntu/nfs/none/w08.7.21.45_aa/singletest Error: (string-split) bad argument type - not a string: #f Call history: margs.scm:17: hash-table-ref/default megatest.scm:931: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:934: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:937: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:940: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:946: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:947: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:948: conc megatest.scm:952: get-environment-variable megatest.scm:952: string-split <-- ; tracing tasks:server-lock-slot | |||||
f1ce13e29b | 2014-02-13 17:59:25 | Code_Defect | Open | setlog crashes if run in wrong directory. | |
chlr12706> megatest -step showresults -setlog results.html :state end :status 0 shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory Error: (current-directory) cannot retrieve current directory Call history: megatest.scm:316: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:333: args:get-arg margs.scm:17: hash-table-ref/default megatest.scm:348: hash-table-keys megatest.scm:346: lset-intersection megatest.scm:352: setup-for-run launch.scm:422: hash-table? launch.scm:425: args:get-arg margs.scm:17: hash-table-ref/default launch.scm:427: get-environment-variable launch.scm:424: find-and-read-config configf.scm:253: ##sys#get-keyword configf.scm:253: ##sys#get-keyword configf.scm:253: ##sys#get-keyword configf.scm:254: current-directory <-- chlr12706> cd $PWD chlr12706> megatest -step showresults -setlog results.html :state end :status 0 | |||||
71cf4cf1bc | 2014-02-13 00:04:26 | Code_Defect | Open | single step not working | |
Warning (#<thread: ezstep run single step gencurrgds&g...Warning (#<thread: ezstep run single step gencurrgds>): in thread: unbound variable: run-id Call history: fs-transport.scm:42: debug:print-info common_records.scm:60: debug:debug-mode fs-transport.scm:43: db:process-queue-item db.scm:1849: g2314 db.scm:1850: g2318 db.scm:1851: g2322 db.scm:1852: g2326 db.scm:1853: alist-ref db.scm:1855: debug:print-info common_records.scm:60: debug:debug-mode db.scm:1865: debug:print-info common_records.scm:60: debug:debug-mode db.scm:1866: server:reply server.scm:108: debug:print-info common_records.scm:60: debug:debug-mode ezsteps.scm:167: cdb:roll-up-pass-fail-counts <-- shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory 4:58 PM | |||||
e1c04aa7aa | 2013-11-05 16:57:08 | Code_Defect | Open | Add test for handling corrupted or non-readable testdat.db | |
03dfedbb23 | 2013-11-04 21:55:15 | Code_Defect | Open | output from launcher script into mt_launch.log appears to not retain any newlines. | |
58552973a3 | 2013-11-02 17:08:19 | Code_Defect | Open | Crash on db access to testdat.db | |
258ecdb207 | 2013-08-17 06:34:40 | Code_Defect | Open | Crash in gui going from Run Summary to Run control | |
Launching /tmp/megatest/tests/fdktestqa/simplelinks/a/bigrun2/a/bigrun/890 Error: (hash-table-ref) hash-table does not contain key tests-info #<hash-table (2)> Call history: dashboard.scm:1053: iup-base#attribute-set! dashboard.scm:1055: iup-base#attribute-set! dashboard.scm:1342: current-milliseconds dashboard.scm:1389: mutex-lock! dashboard.scm:1391: mutex-unlock! dashboard.scm:1381: mutex-lock! dashboard.scm:1385: mutex-unlock! dashboard.scm:1388: dashboard:run-update dashboard.scm:1308: file-modification-time dashboard.scm:1309: file-modification-time dashboard.scm:1310: current-seconds dashboard.scm:1311: dashboard:recalc dashboard.scm:1296: current-milliseconds dashboard.scm:1389: mutex-lock! dashboard.scm:1391: mutex-unlock! dashboard.scm:813: hash-table-ref | |||||
89c0faa86d | 2013-08-05 18:24:21 | Code_Defect | Open | scheme not evaluating properly in megatest.config | |
[evn-override] # BEQASCRIPTS #{scheme (print *toppath*)}/scripts | |||||
36dd7d5d93 | 2013-07-23 04:06:14 | Code_Defect | Open | Handling of script creation in test creation wizard is clumsy | |
================== Next we need to get the variables and values you wish to iterate this test over (blank for none) Enter the variable name: EGG_NAME Enter the space separated list of values for EGG_NAME: matchable readline apropos base64 regex-literals format "regex-case" "test" coops trace csv dot-locking posix-utils posix-extras directory-utils hostinfo tcp rpc csv-xml fmt json md5 Enter the variable name: Hint; use .sh extension on the script names and we'll create placeholder scripts.#<unspecified>#<unspecified>#<unspecified>#<unspecified> matt added on 2013-07-21 22:32:16 UTC: ================== Now to enter the one or more steps that make up your test, note; you can add more later Enter the name for this step (blank to stop): matt added on 2013-07-23 04:06:14 UTC: Executable bits not set on scripts | |||||
cea380846b | 2013-07-22 01:56:53 | Code_Defect | Open | Test steps are not being cleared (regression?) when re-running without CLEAN | |
83eb0489cd | 2013-07-21 22:20:35 | Code_Defect | Open | Create area wizard fails to create directory - should detect calculated dirs | |
================== Now you need an initial place to store your runs. These are called "disks" and you can add more at any time. To get going provide a writeable directory name. Enter your test runs directory: #{getenv MT_TEST_RUN_AREA}/../runs WARNING: you have specified a path #{getenv MT_TEST_RUN_AREA}/../runs that does not exist. Attempting to create it... Error: (create-directory) cannot create directory - File exists: "#{getenv MT_TEST_RUN_AREA}/.." Call history: genexample.scm:49: read-line genexample.scm:51: directory? genexample.scm:57: conc genexample.scm:57: file-exists? genexample.scm:68: print genexample.scm:81: display genexample.scm:82: read-line genexample.scm:84: string-split genexample.scm:84: g25 genexample.scm:84: g25 genexample.scm:87: print genexample.scm:89: display genexample.scm:90: read-line genexample.scm:91: directory? genexample.scm:93: print genexample.scm:94: create-directory <-- | |||||
b340dd6ecc | 2013-07-19 23:27:33 | Code_Defect | Open | runs and links directories are not found if relative. causes crash | |
3d3046b2c2 | 2013-05-09 23:01:33 | Code_Defect | Open | Missing escaping in dashboard test selector | |
"SELECT id,run_id,testname,state,status,event_time,host,cpuload,diskfree,uname,rundir,item_path,run_duration,final_logf,comment FROM tests WHERE run_id=? AND ((testname LIKE '%if %'' AND item_path LIKE '%')) ;" Call history: db.scm:564: string-intersperse tests.scm:100: db:patt->like db.scm:560: ##sys#get-keyword db.scm:564: g779 substring-index db.scm:566: conc db.scm:564: string-intersperse tests.scm:101: conc tests.scm:104: reverse tests.scm:104: append tests.scm:104: string-intersperse db.scm:796: conc db.scm:792: conc db.scm:802: debug:print-info common_records.scm:58: debug:debug-mode db.scm:803: sqlite3#for-each-row <-- | |||||
d68357ce8d | 2013-05-01 17:17:43 | Code_Defect | Open | running -test-status to set CHECK in a linked test sets FAIL | |
../envqa/tests/dumpndiffcdf/main.csh:megatest -test-status : state COMPLETED : status CHECK -setlog cdfdiff_prim/index.html | |||||
d4e2e5ab37 | 2013-04-24 23:21:44 | Code_Defect | Open | STATE/STATUS logic needs correction. Some transitions are resulting in UNKNOWN | |
main test still says UNKNOWN If test is WARN, top-level should also be WARN ok. So SKIP is working as expected wrt item, but parent level test status is not correct (UNKNOWN) Ok. So the rollup is not correct Let me check that. For parent test, I think the conditions should be: All item PASS, parent PASS All item PASS or SKIP, parent PASS one item WARN, rest PASS/SKIP, parent WARN one item FAIL, parent FAIL one item WAIVED, no fail, parent WAIVED precedence is: FAIL, WARN, CHECK, PASS The following rules need to apply to megatest for status for parent tests with items 1 FAIL item parent test FAIL no FAIL, 1 CHECK parent test CHECK no FAIL, no CHECK, 1 WAIVED parent test WAIVED no FAIL, no CHECK, no WAIVED, 1 WARN parent test WARN no FAIL, no CHECK, no WAIVED, no WARN, 1 SKIP parent test PASS all SKIP parent test SKIP all PASS parent test PASS Precedence order is: FAIL => CHECK => WAIVED => WARN => PASS => SKIP 1 corner case: If all items SKIP, parent is SKIP. So if total number of ITEMS and total number if SKIP match, then parent is SKIP. SKIP is a lower priority than PASS as it reflects a preemptive cut of a PASS condition (nothing was actually checked/done) whereas PASS implies actual work to QA. matt added on 2013-04-24 23:21:44 UTC: The following rules need to apply to megatest for status for parent tests with items 1 FAIL item parent test FAIL no FAIL, 1 CHECK parent test CHECK no FAIL, no CHECK, 1 WAIVED parent test WAIVED no FAIL, no CHECK, no WAIVED, 1 WARN parent test WARN no FAIL, no CHECK, no WAIVED, no WARN, 1 SKIP parent test PASS all SKIP parent test SKIP all PASS parent test PASS Precedence order is: FAIL => CHECK => WAIVED => WARN => PASS => SKIP 1 corner case: If all items SKIP, parent is SKIP. So if total number of ITEMS and total number if SKIP match, then parent is SKIP. SKIP is a lower priority than PASS as it reflects a preemptive cut of a PASS condition (nothing was actually checked/done) whereas PASS implies actual work to QA. | |||||
5a591737fb | 2013-03-07 00:07:35 | Code_Defect | Open | getenv USER broken, -waive, -rerun | |
o Error loading runconfigs that uses #{getenv USER} definition Failing to locate targets defined in unloaded runconfigs o –show-config => dumps (STDOUT) contents of megatest.config post-processing o –show-runconfig [–target <target>] => same but for runconfigs o –load <script> => scheme script (exits after execution) o –target <target> :runname <runname> -testpatt <testpatt> -waive <comment> -state COMPLETED –status FAIL o Reset FAIL -> NOT_STARTED o –target <target> :runname <runname> -set-state-status NOT_STARTED,n/a :state COMPLETED :status FAIL –testpatt % make fail_reset/fail_rerun matt added on 2013-03-07 00:07:35 UTC: ./runconfigs.config:[include ./configs/#{getenv USER}.runconfigs.config] | |||||
96d8a782e9 | 2013-02-11 05:46:38 | Code_Defect | Open | Tests; ezlog_fail, ezlog_warn, logpro_required result in PASS if logpro not avail on PATH | |
290d262ed3 | 2013-01-29 21:13:47 | Code_Defect | Open | megatest -generate-test crashes if script has spaces | |
[ ] megatest -generate-test [ ] generate test issue - scripts vs. a command line. Look for |, space, quotes, / as signature of # Add additional steps here. Format is "stepname script" [ezsteps] getrepo fsl repo get `echo $TECH|sed 's/^p12/fdk/'` oalibs co_rel (cd oalibs;fsl co $RELEASE) convert convertall.sh Error: (open-output-file) cannot open file - No such file or directory: "../tests/csv_gen/fsl repo get `echo $TECH|sed 's/^p12/fdk/'` oalibs.sh" Call history: g210219 genexample.scm:240: print genexample.scm:241: print genexample.scm:242: get-environment-variable genexample.scm:242: print genexample.scm:243: get-environment-variable genexample.scm:243: print genexample.scm:244: print genexample.scm:245: print genexample.scm:246: print g245251 genexample.scm:251: conc genexample.scm:251: with-output-to-file genexample.scm:253: print genexample.scm:254: conc genexample.scm:254: with-output-to-file | |||||
894f74c997 | 2012-10-11 15:56:18 | Code_Defect | Open | Cannot set test status from commandline for parent of iterated test | |
db6c35ee0c | 2012-04-20 05:50:00 | Code_Defect | Open | removal of last item dir not happening in -remove-runs, could be link is not created | |
Remove runs on test_mt_vars and item 5 will not be deleted | |||||
630ba8d5a6 | 2012-04-11 20:29:47 | Code_Defect | Open | Running a test with pre-dependecies and -itempatt causes forever run | |
44c3549dab | 2011-11-10 22:25:10 | Code_Defect | Open | dashboard refresh race condition. last update misses occasionally |