Hi Benjamin,

Yes, I believe the configuration matrix needs to add an entry similar to :

Configuration Matrix
--verbose --disable-libtool-wrappers --disable-parallel-test-execution

Configuration matrix must be living somewhere private to Mesos or in 
Jenkins(using configuration matrix 
 as I am unable to find configuration variables such as 
“MESOS_TEST_AWAIT_TIMEOUT” environment being referred in Mesos source code.

As mentioned here<https://github.com/apache/mesos/pull/449#issue-1455059508>, 
above configuration has also been tested as well.

Please let me know if there is any way I can help to update configuration 

Thanks & Regards,

From: Benjamin Mahler <bmah...@apache.org>
Date: Tuesday, 12 March 2024 at 4:43 AM
To: dev@mesos.apache.org <dev@mesos.apache.org>
Cc: Rishi Misra <ri...@ca.ibm.com>
Subject: [EXTERNAL] Re: Add s390x support for Mesos CI
presumably you want to update the configuration matrix here?


not sure where this configuration lives though

On Mon, Mar 11, 2024 at 1:28 AM Yasir Ashfaq <yasir.ashf...@ibm.com.invalid>

> Hi All,
> We recently added changes(https://github.com/apache/mesos/pull/449 ) to
> provide s390x CI support for Mesos.
> Even though the changes are merged, Mesos CI has not been enabled yet.
> As per https://issues.apache.org/jira/browse/INFRA-21433 , we have
> provided apache four s390x nodes, hence, same nodes can be used to enable
> Apache Mesos CI as well.
> Could you please let us know if there is anything further required from
> our side to enable Mesos CI support for s390x.
> Thanks & Regards,
> Yasir

Reply via email to