Re: [PATCH v2 6/7] oeqa/selftest/cases/rust.py: Rust oe-selftest script.

["Alexander Kanavin" <alex.kanavin@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

Thanks, can you please look into the error? The line where it happens and
the way to get a backtrace is right there :)
There's no reason it shouldn't work.

Alex

On Mon, 17 May 2021 at 15:21, Vinay Kumar <vinay.m.engg@gmail.com> wrote:

> Hi Alex,
>
> Error on qemu  image (ex. Aarch64) booted with tap interface.
> ===========================
> root@qemuarm64:~# ./remote-test-server
> starting test server
> thread 'main' panicked at 'TcpListener::bind(bind_addr) failed with
> Cannot assign requested address (os error 99)',
> src/tools/remote-test-server/src/main.rs:90:20
> note: run with `RUST_BACKTRACE=1` environment variable to display a
> backtrace
> ===========================
>
> On Mon, May 17, 2021 at 5:16 PM Alexander Kanavin
> <alex.kanavin@gmail.com> wrote:
> >
> > On Mon, 17 May 2021 at 13:34, Vinay Kumar <vinay.m.engg@gmail.com>
> wrote:
> >>
> >> "remote-test-server" on qemu-image with a tap interface throws an error.
> >> The emulators for rust testing are with tcp port forwarding so used
> >> slirp method with added rust port.
> >
> >
> > I'm not sure I understand - what kind of error? In both cases the server
> starts listening on a port, so in slirp scenario the address is
> 127.0.0.1:12345 (prone to breakage if something else on the build host
> took that port btw, including another instance of the same test), in tap it
> would be 192.168.7.2:12345. For the client you simply supply that via
> TEST_DEVICE_ADDR. No?
> >
> > Alex
>

[-- Attachment #2: Type: text/html, Size: 2225 bytes --]