Skip to content
This repository has been archived by the owner on Aug 5, 2022. It is now read-only.

CI: Use Docker container from crops:yocto/ubuntu-16 #220

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

okartau
Copy link
Contributor

@okartau okartau commented Jul 1, 2017

Signed-off-by: Olev Kartau [email protected]

@okartau okartau force-pushed the try-yocto-dockerfile branch 2 times, most recently from c2cb12c to b488db1 Compare July 1, 2017 21:27
@okartau
Copy link
Contributor Author

okartau commented Jul 1, 2017

when building in Ubuntu-14.04 container, build fails with "let: not f ound"
points to real issue?

Waiting for generation of signing key refkit-development-signing@key...
/srv/jenkins/workspace/ci-2017-07-01_14-30-15-build-1852/build/tmp-glibc/work/intel_corei7_64-refkit-linux/refkit-image-gateway/1.0-r0/temp/run.do_generate_signing_keys.35867: 134: /srv/jenkins/workspace/ci-2017-07-01_14-30-15-build-1852/build/tmp-glibc/work/intel_corei7_64-refkit-linux/refkit-image-gateway/1.0-r0/temp/run.do_generate_signing_keys.35867: let: not found

@okartau
Copy link
Contributor Author

okartau commented Jul 1, 2017

let is bashism, and Ubuntu uses dash, right

@okartau okartau requested review from klihub and mythi July 1, 2017 22:26
@pohly
Copy link
Contributor

pohly commented Jul 3, 2017

@mythi, @klihub: Instead of fixing the bash dependency in refkit-signing-keys.bbclass I think we should get rid of it entirely and replace the mechanism with pre-generated keys + script for manually creating them, as suggested before. Do you agree? @klihub, can you prepare a PR for that?

@mythi
Copy link
Contributor

mythi commented Jul 3, 2017 via email

@okartau okartau changed the title CI: Try to use Docker container from crops:yocto/ubuntu-14 CI: Try to use Docker container from crops:yocto/ubuntu-16 Jul 8, 2017
@okartau
Copy link
Contributor Author

okartau commented Jul 8, 2017

switching to Ubuntu-16.04 base from crops

@okartau
Copy link
Contributor Author

okartau commented Jul 10, 2017

note that CI build of this does not complete, but remains hanging until aborted manually

@pohly
Copy link
Contributor

pohly commented Jul 10, 2017 via email

@okartau
Copy link
Contributor Author

okartau commented Jul 10, 2017

hm, perhaps I was too quick to abort. But two previous builds of this PR had run for 14 h amd 9.5 h without reaching end, so I made guess this has hanged (after 5.5h.) We can give it one more run and wait really long if needed.

@okartau
Copy link
Contributor Author

okartau commented Jul 10, 2017

About sstate: I checked connectivity while next build was running, seems OK.
I verified that in attached-to-docker-session shell using wget, I can read files from sstate.
Another cross-check: refkit server http log has entries that this builder was doing many HEAD operations and result was 200:
example:

10.237.71.144 - - [10/Jul/2017:20:25:47 +0300] "HEAD /download/bb-cache/sstate/fa/sstate%3Agnu-efi%3Acorei7-64-refkit-linux%3A3.0.5%3Ar0%3Acorei7-64%3A3%3Afaef5002cfad1f1a9222e16a4d89c335_package.tgz HTTP/1.1" 200 - "-" "Python-urllib/3.4"

Seems, bitbake can check presence get sstate files, also wget, but for some reason does not use those files.

@okartau
Copy link
Contributor Author

okartau commented Jul 11, 2017

I have now contradicting results about builder accessing sstate_mirror over http.
Two jobs running today morning of this PR, and both builders did not make any requests to http server,
based on server apache logs.
Again, I cross checked, atached process to docker container, that wget of sstate dir works (and gets logged in apache access log)

@pohly pohly mentioned this pull request Jul 11, 2017
@intel intel deleted a comment from pohly Jul 12, 2017
@intel intel deleted a comment from pohly Jul 12, 2017
@okartau okartau force-pushed the try-yocto-dockerfile branch 4 times, most recently from 9c96c3f to 5a2f6cd Compare July 13, 2017 08:17
@okartau okartau changed the title CI: Try to use Docker container from crops:yocto/ubuntu-16 CI: Use Docker container from crops:yocto/ubuntu-16 Jul 13, 2017
@okartau okartau force-pushed the try-yocto-dockerfile branch 2 times, most recently from 6151f77 to 56b63d2 Compare July 21, 2017 11:02
@okartau okartau force-pushed the try-yocto-dockerfile branch 2 times, most recently from c9af5e5 to c87e5ff Compare July 28, 2017 05:45
@okartau okartau force-pushed the try-yocto-dockerfile branch 3 times, most recently from 031387e to c76936d Compare August 6, 2017 14:24
@okartau okartau force-pushed the try-yocto-dockerfile branch 4 times, most recently from 6550140 to c55d8d2 Compare August 16, 2017 08:36
@okartau okartau force-pushed the try-yocto-dockerfile branch 2 times, most recently from 0f6f2f5 to f5b97e3 Compare August 23, 2017 05:56
@okartau okartau force-pushed the try-yocto-dockerfile branch 4 times, most recently from 37e0648 to 41d4634 Compare September 6, 2017 18:34
@okartau okartau force-pushed the try-yocto-dockerfile branch 3 times, most recently from 5ee5600 to 0023655 Compare September 18, 2017 05:25
@okartau
Copy link
Contributor Author

okartau commented Oct 12, 2017

test this please, unrelated nftables error

@okartau
Copy link
Contributor Author

okartau commented Oct 20, 2017

test this please

@okartau okartau force-pushed the try-yocto-dockerfile branch 2 times, most recently from c804e49 to f9d13c9 Compare November 23, 2017 11:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants