Revision 5ee2ebcc1afd2103924629a7c13a101e4021308a authored by Robert Ma on 05 April 2018, 19:32:29 UTC, committed by jgraham on 05 April 2018, 19:32:29 UTC
The root cause is that we use the up-to-date manifest and rely on the files on the head of master, so the test will fail whenever the file we are asserting is renamed (which unfortunately happened at bf17459a71ff4d1ea280bae54dd046ecf86e0628). This PR doesn't fix the root cause, but instead switches to a relatively stable test file (`infrastructure/reftest-wait.html`). Hopefully this will hold in the forseeable future.
1 parent 1fd16de
Computing file changes ...
