Stream: git-wasmtime

Topic: wasmtime / PR #2481 Update spec tests

view this post on Zulip Wasmtime GitHub notifications bot (Dec 04 2020 at 23:52):

abrown opened PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since this has not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 04 2020 at 23:52):

abrown requested fitzgen for a review on PR #2481.

view this post on Zulip Wasmtime GitHub notifications bot (Dec 04 2020 at 23:53):

abrown edited PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 04 2020 at 23:53):

abrown edited PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime itself?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 16:28):

fitzgen submitted PR Review.

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 16:28):

fitzgen submitted PR Review.

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 17:21):

abrown updated PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime itself?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 17:37):

abrown updated PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime itself?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 17:39):

abrown updated PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime itself?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 17:41):

abrown updated PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime itself?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 17:49):

abrown updated PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime itself?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 17:56):

abrown updated PR #2481 from update-spec-tests to main:

This updates the Wasm spec tests to the commits at https://github.com/WebAssembly/testsuite/pull/37, which brings in some tests for new Wasm SIMD operations. Since the spec tesets have not been updated in a while, it brings in other changes, like those to data.wast which cause a failure:

---- wast::Cranelift::spec::data stdout ----
thread 'wast::Cranelift::spec::data' panicked at 'called `Result::unwrap()` on an `Err` value: failed directive on tests/spec_testsuite/data.wast:290:1

Caused by:
    assert_invalid: expected "unknown memory 1", got "WebAssembly failed to compile

    Caused by:
        0: WebAssembly translation error
        1: Invalid input WebAssembly code at offset 21: Data segment extends past end of the data section"', /home/abrown/Code/wasmtime/target/debug/build/wasmtime-cli-02b4b8fc65746038/out/wast_testsuite_tests.rs:470:14

failures:
    wast::Cranelift::spec::data

test result: FAILED. 264 passed; 1 failed; 48 ignored; 0 measured; 0 filtered out

Is this an error stringifying problem or a problem in Wasmtime itself?

view this post on Zulip Wasmtime GitHub notifications bot (Dec 07 2020 at 18:59):

abrown merged PR #2481.

Last updated: Dec 23 2024 at 13:07 UTC