Ticket Hash: | 42d22a56b899f44f9db5e2c7d6c2c4bb61c1fb20 | |||
Title: | guard against this: basic -run fails with cryptic error when user login prints things to stdout. | |||
Status: | Verified | Type: | Feature_Request | |
Severity: | Important | Priority: | Immediate | |
Subsystem: | Resolution: | Open | ||
Last Modified: | 2019-07-29 17:22:48 | |||
Version Found In: | v1.6531 | |||
User Comments: | ||||
bb added on 2019-07-29 22:26:33:
procedure: 1) setup area with megatest -create-megatest-area no change to megatest.config 2) create runconfig: ##### [default] ALLTESTS verdi_gui_t [bb_f65] SDE_ROOT /eng3/bjbarcla/work/verdi_1215/cpwork/ip-sde-1.0-f65 ##### 3) created testconfig ###### [itemstable] proj willard nsc_ip repo asic-willard-a0 ip-nsc-2.1 relpath arb/verif/testsuites/bringup xor/verif/testsuites/bringup target arb_mr_test_check axi_agent_test_sim sderel f61 f65 [ezsteps] run run.csh [logpro] run ;; (expect:skip in "LogFileBody" = 0 "SKIPME" \ #/skipping. does not apply/) ######### megatest -run -testpatt % -target bb_f65 -runname ww31.1b -clean-cache /nfs/fm/disks/fm_nvm_1184/dvtools_ENV_users/bjbarcla/WORK/mt/megatest/bin/.11/mtest -run -testpatt % -target bb_f65 -runname ww31.1b -clean-cache INFO: (0) No cached megatest or runconfigs files found. None removed. INFO: Trying to start server (megatest -server 10.96.27.151 -m testsuite:verdi_int_reg) ... Error: (-) bad argument type: Adding Call history: common_records.scm:140: debug:debug-mode common.scm:1624: current-seconds common.scm:1624: file-change-time common.scm:1626: with-input-from-file numbers.scm:1720: %string->compnum numbers.scm:1672: scan-real numbers.scm:1671: scan-ureal numbers.scm:1603: scan-digits+hashes numbers.scm:1549: scan-digits numbers.scm:1531: lp numbers.scm:1531: lp numbers.scm:1548: g1937 common.scm:1620: k2830 common.scm:1620: g2834 common.scm:1870: max common.scm:1873: max <-- bb added on 2019-07-29 23:12:19: root cause - cshrc echoed something to stdout. recommend guarding against that... bb added on 2019-07-29 23:13:30: errant stdout captured to <ip>-cpu-load.log and causes crash mrwellan added on 2019-07-29 23:22:48: Issue occurs when ssh to machine spits out extraneous output. We expect this to be a non-issue in Megatest 2.0. Leaving this ticket open until then. |