[ 
https://issues.apache.org/jira/browse/SSHD-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031225#comment-18031225
 ] 

Thomas Wolf commented on SSHD-1347:
-----------------------------------

Thanks for posting the test outputs. The ones from the failing test would have 
sufficed :).

Test output in 
{{org.apache.sshd.client.proxy.ProxyHttpIntegrationTest-output.txt}} shows:
{code:java}
09:30:20.583 | WARN  | main             | t.vimagick/tinyproxy:latest      | 
org.testcontainers.containers.GenericContainer                    477 | The 
architecture 'amd64' for image 'vimagick/tinyproxy:latest' (ID 
sha256:72b441b95ee1e641af948f68f09492f9f795ead72b73954414e339168c98ad8c) does 
not match the Docker server architecture 'arm64'. This will cause the container 
to execute much more slowly due to emulation and may lead to timeout failures.
09:30:20.587 | INFO  | stream-977377447 | a.s.c.p.ProxyHttpIntegrationTest | 
org.testcontainers.containers.output.Slf4jLogConsumer              66 | STDOUT: 
CONNECT   Oct 19 13:30:20.586 [1]: Connect (file descriptor 8): 151.101.2.132
09:30:20.587 | INFO  | stream-977377447 | a.s.c.p.ProxyHttpIntegrationTest | 
org.testcontainers.containers.output.Slf4jLogConsumer              66 | STDOUT: 
ERROR     Oct 19 13:30:20.587 [1]: read_request_line: Client (file descriptor: 
8) closed socket before read.
09:30:20.587 | INFO  | stream-977377447 | a.s.c.p.ProxyHttpIntegrationTest | 
org.testcontainers.containers.output.Slf4jLogConsumer              66 | STDOUT: 
ERROR     Oct 19 13:30:20.587 [1]: Error reading readable client_fd 8
09:30:20.587 | INFO  | stream-977377447 | a.s.c.p.ProxyHttpIntegrationTest | 
org.testcontainers.containers.output.Slf4jLogConsumer              66 | STDOUT: 
WARNING   Oct 19 13:30:20.587 [1]: Could not retrieve request entity
09:30:20.590 | WARN  | ontainers-wait-0 | nternalCommandPortListeningCheck | 
iners.containers.wait.internal.InternalCommandPortListeningCheck   58 | An 
exception while executing the internal check: 
Container.ExecResult(exitCode=128, stdout=cannot exec in a stopped state: 
unknown
, stderr=)
 {code}
This shows that
 # The vimagick/tinyproxy container image is amd64-only; it has no support for 
ARM. The test fails because
 # tinyproxy inside the container fails to start.

I'll have to find a better container for tinyproxy that supports both 
arm64/x86_64 and aarch64. Unfortunately there is no "official" tinyproxy 
container. I'll give 
[ajoergensen/tinyproxy|https://hub.docker.com/r/ajoergensen/tinyproxy/tags] a 
try; that one is multi-architecture.

> Resolve build failures in apache-sshd-3.0.0-M2 RC
> -------------------------------------------------
>
>                 Key: SSHD-1347
>                 URL: https://issues.apache.org/jira/browse/SSHD-1347
>             Project: MINA SSHD
>          Issue Type: Bug
>            Reporter: Gary D. Gregory
>            Priority: Major
>         Attachments: surefire-reports-nio2.zip
>
>
> Based on the source zip, I am getting failures:
> [https://gist.github.com/garydgregory/7bf944ab52e0c4343e07217c605460ab]
> Output of {{apache-sshd-3.0.0-M2/sshd-test/target/surefire-reports-nio2}} is 
> zipped and attached.
> Using:
> {noformat}
> openjdk version "25" 2025-09-16
> OpenJDK Runtime Environment Homebrew (build 25)
> OpenJDK 64-Bit Server VM Homebrew (build 25, mixed mode, sharing)
> Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
> Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
> Java version: 25, vendor: Homebrew, runtime:
> /opt/homebrew/Cellar/openjdk/25/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "15.7.1", arch: "aarch64", family: "mac"
> Darwin ****-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Mon
> Aug 11 21:15:09 PDT 2025;
> root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T6041 arm64
> Docker version 28.4.0, build d8eb465
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to