equal
deleted
inserted
replaced
1 Bash test results are stored in test/*/test-64-results. They are then filtered |
1 Bash test results are stored in test/*/test-64-results. They are then filtered |
2 by COMPONENT_TEST_TRANSFORMS to make the test produce stable/reproducible |
2 by COMPONENT_TEST_TRANSFORMS to make the test produce stable/reproducible |
3 results. Unfortunatelly COMPONENT_TEST_TRANSFORMS remove any problems |
3 results. Currently the only test which is not sometimes passing is 'run-trap'. |
4 encountered too. This is not ideal and should be fixed. The problem is that |
4 Explanation is in the test output itself, and this is what the output looks like: |
5 bash tests are sensitive to environment they are executed in (your ~/.bash* |
|
6 files for example). It's not easy to tell that bash tests finished |
|
7 successfully, you have to read it through. |
|
8 |
5 |
9 To compare the results before and after a fix one has to store test-64-results |
6 warning: UNIX versions number signals and schedule processes differently. |
10 file and compare it to the one generated after your change. |
7 warning: If output differing only in line numbers is produced, please |
|
8 warning: do not consider this a test failure. |
|
9 71d70 |
|
10 < +[8] cat |
|
11 72a72 |
|
12 > +[8] cat |
|
13 |
|
14 |
|
15 COMPONENT_TEST_TRANSFORMS thus remove this test output. When testing bash it is |
|
16 necessary to observe full test-64-results. |
|
17 |
|
18 |
|
19 To test new version of bash installed on new machine I did: |
|
20 |
|
21 - install new bash |
|
22 - reboot |
|
23 - svcs -x # to see if it caused any issue |
|
24 - bash --version |
|
25 - to see if we are testing right bash version |
|
26 |