Commit 32f2657
committed
test(nodeenv): make the git-bash probe report why it failed
The first CI run of the new job failed with a bare exit 1 and no
diagnostic: the probe ran through `bash -c` with the script and the
environment path as arguments, so the quoting rules of two command line
parsers sat between the test and what the shell ran, and stderr was not
captured at all. It now writes the probe to a file, traces it with
`set -x` and puts both streams into the assertion message.
The direct call guard matches on $0, which a shell reports in the form
it was given; the test was passing the native `C:\...` path, which no
posix shell would produce.1 parent e7c7092 commit 32f2657
2 files changed
Lines changed: 24 additions & 11 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
104 | 104 | | |
105 | 105 | | |
106 | 106 | | |
107 | | - | |
108 | | - | |
109 | | - | |
110 | | - | |
111 | | - | |
112 | | - | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
113 | 117 | | |
114 | | - | |
| 118 | + | |
115 | 119 | | |
116 | | - | |
117 | | - | |
118 | | - | |
| 120 | + | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
119 | 130 | | |
120 | 131 | | |
121 | 132 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
496 | 496 | | |
497 | 497 | | |
498 | 498 | | |
499 | | - | |
| 499 | + | |
| 500 | + | |
| 501 | + | |
500 | 502 | | |
501 | 503 | | |
502 | 504 | | |
| |||
0 commit comments