On 06.08.21 10:50, Jan Kiszka via Xenomai wrote:
> On 02.08.21 17:43, Jan Kiszka via Xenomai wrote:
>> From: Jan Kiszka <jan.kis...@siemens.com>
>>
>> This is a temporary hack: Our AWS runners see a lot of DNS errors for
>> deb.debian.org. Let's see if they are less with this server.
>>
>> Signed-off-by: Jan Kiszka <jan.kis...@siemens.com>
>> ---
>>
>> Seems to work, though only one run passed so far. Go this way for now?
>>
>> ci/gitlab-ci-base.yml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/ci/gitlab-ci-base.yml b/ci/gitlab-ci-base.yml
>> index 2638dec..ce9c800 100644
>> --- a/ci/gitlab-ci-base.yml
>> +++ b/ci/gitlab-ci-base.yml
>> @@ -39,6 +39,7 @@ default:
>> extends: .add-proxy-config
>> stage: build
>> script:
>> + - sudo sh -c "echo 'nameserver 8.8.8.8' > /etc/resolv.conf"
>> - echo "Building
>> kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml"
>> - kas build
>> kas.yml:board-${TARGET}.yml${XENOMAI_BUILD_OPTION}${LINUX_BUILD_OPTION}${BUILD_OPTIONS}:opt-debug.yml
>> - if [ -n "${USE_S3_BUCKET}" ]; then scripts/deploy_to_aws.sh
>> ${TARGET}; fi
>>
>
> Seems you found the reason in our AWS setup. I'm dropping this from next
> again to confirm that we are safe.
>
Back and forth: As the issue reoccurred with this removed (only the one
before the image runs was apparently resolved), this is back into next
again. So far, it looks good.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
