-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI fails on azure 32 bit linux Linux_i386: sudo apt-fast install fails #17325
Comments
https://dev.azure.com/nim-lang/Nim/_build/results?buildId=14079&view=logs&jobId=ba7bbfa4-f55c-5c34-6d52-1b6b4edd3f37&j=ba7bbfa4-f55c-5c34-6d52-1b6b4edd3f37&t=38200048-f2b3-5d1c-03e3-3014d58a3656 shows the 1st place where there's a problem: instead of:
we get:
note that we should abort right here after |
Hmm, In bash without |
I think it did but not using
as I've observed in #17326, we need to add
|
I would like to avoid this if possible. |
From nim-lang#17325 (comment), it appears that apt-fast is ignoring errors.
In the future I'll enginner a docker image as CI for nim, which should avoid all of these stupid issues with If you want to upgrade the ubuntu version @timotheecour, please upgrade it for all architectures. |
=> replied in #17327 (comment) |
Re-opening because the hotfix #17327 worked for 2 days but the i386 linux problem re-occured even though its now using ubuntu 18.04
/cc @alaviss since you've created the pipeline for i386 :-)
option 1
option 2
links
|
@timotheecour try removing the manual pinning I made. That pinning was targeted for Ubuntu 16.04. |
I've tried this but it doesn't seem to work. Please disable 32 bit Linux testing for now, I'll build a container image later for CI. |
i'm pretty sure this is among the many things i've tried and IIRC it didnt' work; it was trying it again but azure is slow due to a temporary downtime refs https://status.dev.azure.com/ (EDIT: indeed I've checked again that this doesn't work) disabling 32bit linux is pure cosmetics though, we could do it as last resort but I can do something better that just disables 3 tests, refs #17359 tests/async/tasyncssl.nim see errors i'm getting here: #17359 (comment) the problem is right now the azure outage prevents further testing, hopefully resolved in a few minutes/hours |
Multiarch doesn't work on Azure's hosted VM for some odd reasons, (ref nim-lang#17325).
Got a container image rolling: https://github.com/users/alaviss/packages/container/package/nim-ci I haven't managed to get this working with Azure but you can see my ARM CI for the container in action: https://cloud.drone.io/alaviss/Nim/14/2/2 We will want to move our Linux CI image to this, given that it's a more controlled environment compared to the VM images provided by CI services. |
re-opening this, sadly: i386 fails again a
probably another upstream issue; our setup for i386 emulation on azure is fragile indeed. |
I disabled i386 again, see #17963 future workthis keeps happening so we need a more robust fix.
(all 3 are still WIP) |
I'm seeing:
nim-lang.Nim (packages Linux_i386) Failing after 58s — packages Linux_i386 failed
in several unrelated PRs (eg #17257 (comment))
eg https://dev.azure.com/nim-lang/255dfe86-e590-40bb-a8a2-3c0295ebdeb1/_apis/build/builds/14075/logs/38
(refs #3123 (comment))
refs:
The text was updated successfully, but these errors were encountered: