Wait to make the test system correctly recognize the 'bar' file as touched after the next build run. Without the wait, the next build run may rebuild the 'bar' file with the new and the old file modification timestamp too close to each other - which could, depending on the current
(t)
| 9 | |
| 10 | |
| 11 | def wait_for_bar(t): |
| 12 | """ |
| 13 | Wait to make the test system correctly recognize the 'bar' file as |
| 14 | touched after the next build run. Without the wait, the next build run may |
| 15 | rebuild the 'bar' file with the new and the old file modification timestamp |
| 16 | too close to each other - which could, depending on the currently supported |
| 17 | file modification timestamp resolution, be detected as 'no change' by the |
| 18 | testing system. |
| 19 | |
| 20 | """ |
| 21 | t.wait_for_time_change("bar", touch=False) |
| 22 | |
| 23 | |
| 24 | t = BoostBuild.Tester(["-ffile.jam", "-d+3", "-d+12", "-d+13"], pass_d0=False, |
no test coverage detected