Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test-ref tests fail if supplied with --name argument #4092

Closed
mttr opened this issue Nov 24, 2014 · 3 comments
Closed

test-ref tests fail if supplied with --name argument #4092

mttr opened this issue Nov 24, 2014 · 3 comments
Labels

Comments

@mttr
Copy link
Contributor

@mttr mttr commented Nov 24, 2014

...but those same tests pass if I just let it run through all of the ref tests.

Failing:

$ ./mach test-ref --name acid1
Running cpu reftests...
Scanning /home/xxx/servo/tests/ref for manifests

        /home/xxx/servo/tests/ref/basic.list [164 tests]
        /home/xxx/servo/tests/ref/csswg/css21/css21.list [2 tests]

running 1 test
test acid1_a.html == acid1_b.html ... FAILED

failures:

---- acid1_a.html == acid1_b.html stdout ----
        task 'acid1_a.html == acid1_b.html' panicked at 'assertion failed: `(left == right) && (right == left)` (left: `exit code: 1`, right: `exit code: 0`)', tests/reftest.rs:257



failures:
    acid1_a.html == acid1_b.html

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured

Running gpu reftests...
Scanning /home/xxx/servo/tests/ref for manifests

        /home/xxx/servo/tests/ref/basic.list [164 tests]
        /home/xxx/servo/tests/ref/csswg/css21/css21.list [2 tests]

running 1 test
test acid1_a.html == acid1_b.html ... FAILED

failures:

---- acid1_a.html == acid1_b.html stdout ----
        task 'acid1_a.html == acid1_b.html' panicked at 'assertion failed: `(left == right) && (right == left)` (left: `exit code: 1`, right: `exit code: 0`)', tests/reftest.rs:257



failures:
    acid1_a.html == acid1_b.html

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured

Reference tests completed in 0.12s

Passing:

$ ./mach test-ref
Running cpu reftests...
Scanning /home/xxx/servo/tests/ref for manifests

        /home/xxx/servo/tests/ref/basic.list [164 tests]
        /home/xxx/servo/tests/ref/csswg/css21/css21.list [2 tests]

running 166 tests
test acid1_a.html == acid1_b.html ... ok
test abs_float_pref_width_a.html == abs_float_pref_width_ref.html ... ok
...
@jdm jdm added the A-testing label Nov 24, 2014
@mttr
Copy link
Contributor Author

@mttr mttr commented Nov 24, 2014

Blocks #4091

@mttr
Copy link
Contributor Author

@mttr mttr commented Nov 24, 2014

Interestingly, if you run the reftest directly (as in $ ./target/reftest-* cpu tests/ref acid1) the tests pass. So this is starting to look like a mach issue after all. I'll have a look!

@mttr
Copy link
Contributor Author

@mttr mttr commented Nov 24, 2014

Okay. Figured it out. At some point I seriously misread something and misunderstood the way test-ref handles name filtering. There is no --test argument (the fact that it coincidentally worked exactly as expected, test failures aside, was a major source of confusion).

Instead, it looks like mach passes unknown arguments to reftest after an -- (so for what I've been doing: ./target/reftest-* cpu tests/ref acid1 -- --test) which are subsequently passed on to servo. If servo doesn't know how to handle the argument, it explodes behind the scenes--failing the test instead of telling us something went wrong (and why).

The good news is that I can at least fix #4091 now.

@mttr mttr closed this Nov 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.