1 |
A separate list that people can opt-in would make a lot of sense! |
2 |
|
3 |
I tried setting up a OSX based CI... but I wanted to try on a OSX machine |
4 |
first, and I know nothing about Mac's so I failed miserably. |
5 |
|
6 |
I should try to use a VM as I've read in the internet, but that seems quite |
7 |
time consuming to figure it out. |
8 |
|
9 |
I also started very minimally to look into ARM via qemu, also in a CI |
10 |
environment. But it's no priority for me right now, so I also have that |
11 |
paused. |
12 |
|
13 |
On Thu, Jan 17, 2019 at 1:04 AM Fabian Groffen <grobian@g.o> wrote: |
14 |
|
15 |
> Hi Sam, |
16 |
> |
17 |
> Thanks!!!! |
18 |
> |
19 |
> I'm currently assembling my own builds (work in progress) and am |
20 |
> planning to make some log analysis to point out what's wrong. Perhaps |
21 |
> we can integrate the CI runs with the bootstraps on my "hardware". |
22 |
> |
23 |
> I'm planning on releasing details about buildlogs, distfiles used |
24 |
> (possibly allow bootstraps to use it, so we work around the missing |
25 |
> distfiles problem), and have some status overview. I considered email, |
26 |
> but I think it shouldn't be to spammy if sent to a list. Perhaps we can |
27 |
> create a separate list for it though. |
28 |
> |
29 |
> Fabian |
30 |
> |
31 |
> On 17-01-2019 00:59:09 +1100, Sam Pfeiffer wrote: |
32 |
> > Hello, |
33 |
> > |
34 |
> > Given it's the first time I touch Fedora it took a bit of time to get it |
35 |
> working |
36 |
> > (also I had some DNS issues where I couldn't use dnf). |
37 |
> > |
38 |
> > But it's done. |
39 |
> > |
40 |
> > You can check out the jobs at: |
41 |
> > |
42 |
> > For amd64 (Job called bootstrap_on_fedora_rap_off, [1]Dockerfile of the |
43 |
> > job): [2] |
44 |
> https://dev.azure.com/12719821/12719821/_build/results?buildId=451 |
45 |
> > |
46 |
> > For x86 (Job called bootstrap_on_fedora_rap_off, [3]Dockerfile of the |
47 |
> > job): [4] |
48 |
> https://dev.azure.com/12719821/12719821/_build/results?buildId=450 |
49 |
> > |
50 |
> > In 5-6h they should be finished. |
51 |
> > |
52 |
> > In general all the builds are |
53 |
> > here: [5] |
54 |
> https://dev.azure.com/12719821/12719821/_build?definitionId=2&_a=summary |
55 |
> > |
56 |
> > Given this seems to be running quite nicely. Should I add automated |
57 |
> emails when |
58 |
> > builds fail? |
59 |
> > |
60 |
> > I can do it either adding a script that does it or via the CI interface |
61 |
> (I |
62 |
> > think). I won't always be able to check it out quick and make a bug |
63 |
> report, so |
64 |
> > maybe someone else would like to receive the emails about the failures. |
65 |
> > |
66 |
> > On Wed, Jan 16, 2019 at 11:28 PM Michael Haubenwallner <[6] |
67 |
> haubi@g.o> |
68 |
> > wrote: |
69 |
> > |
70 |
> > > On 1/16/19 2:23 AM, Sam Pfeiffer wrote: |
71 |
> > > > Hello Michael, |
72 |
> > > > |
73 |
> > > > Yeah, just tell me which base distro do you want and I'll add a |
74 |
> nightly job |
75 |
> > > with that one. I just need to find a Docker image for it. |
76 |
> > |
77 |
> > > It doesn't really matter, just not Ubuntu (or anything else that does |
78 |
> > > 'multiarch'). |
79 |
> > > I would suggest Fedora though... |
80 |
> > |
81 |
> > > > |
82 |
> > > > Will the final Gentoo Prefix, once bootstrapped, be any different |
83 |
> from the |
84 |
> > > current one I'm bootstrapping? |
85 |
> > |
86 |
> > > Yes: It does not contain sys-libs/glibc and sys-kernel/linux-headers. |
87 |
> > |
88 |
> > > > (To know if I should also publish automated releases of the |
89 |
> bootstrapped |
90 |
> > > Gentoo Prefix). |
91 |
> > |
92 |
> > > Haven't recognized that you do 'publish automated releases', nice! |
93 |
> > |
94 |
> > > As Prefix/Guest is stronger bound to the host OS compared to |
95 |
> Prefix/RAP, |
96 |
> > > binary releases don't feel that useful here - at least to myself. |
97 |
> > |
98 |
> > > Instead, besides x86_64, also x86 (32bit) would be nice - simply using |
99 |
> > > 'linux32': |
100 |
> > > $ PREFIX_DISABLE_RAP=yes linux32 ./bootstrap-prefix.sh /target/prefix |
101 |
> > > noninteractive |
102 |
> > |
103 |
> > > Thanks a lot! |
104 |
> > > /haubi/ |
105 |
> > |
106 |
> > > > |
107 |
> > > > |
108 |
> > > > On Wed, Jan 16, 2019, 04:38 Michael Haubenwallner <[7] |
109 |
> haubi@g.o |
110 |
> > > <mailto:[8]haubi@g.o> wrote: |
111 |
> > > > |
112 |
> > > > Hi Sammy, |
113 |
> > > > |
114 |
> > > > because of Ubuntu inside these build slaves I do understand you |
115 |
> > > currently |
116 |
> > > > perform Prefix RAP bootstraps only - as this is the default |
117 |
> anyway. |
118 |
> > > > |
119 |
> > > > Do you see a chance to perform Prefix Guest bootstraps as well, |
120 |
> > > > even if that would require something other distro than Ubuntu? |
121 |
> > > > |
122 |
> > > > Otherwise, the only difference is to set the |
123 |
> PREFIX_DISABLE_RAP=yes |
124 |
> > > > environment variable when executing bootstrap-prefix.sh. |
125 |
> > > > |
126 |
> > > > Thanks! |
127 |
> > > > /haubi/ |
128 |
> > > > |
129 |
> > > > |
130 |
> > |
131 |
> > -- |
132 |
> > |
133 |
> > Sammy Pfeiffer |
134 |
> > PhD Candidate at The Magic Lab within UTS. |
135 |
> > |
136 |
> > |
137 |
> > |
138 |
> > References: |
139 |
> > 1. |
140 |
> https://github.com/awesomebytes/gentoo_prefix_ci/blob/master/initial_bootstrap/Dockerfile.fedora |
141 |
> > 2. https://dev.azure.com/12719821/12719821/_build/results?buildId=451 |
142 |
> > 3. |
143 |
> https://github.com/awesomebytes/gentoo_prefix_ci_32b/blob/master/initial_bootstrap/Dockerfile.fedora |
144 |
> > 4. https://dev.azure.com/12719821/12719821/_build/results?buildId=450 |
145 |
> > 5. |
146 |
> https://dev.azure.com/12719821/12719821/_build?definitionId=2&_a=summary |
147 |
> > 6. mailto:haubi@g.o |
148 |
> > 7. mailto:haubi@g.o |
149 |
> > 8. mailto:haubi@g.o |
150 |
> > |
151 |
> > read_char: errno==EILSEQ; invalid byte sequence for UTF-8: |
152 |
> -- |
153 |
> Fabian Groffen |
154 |
> Gentoo on a different level |
155 |
> |
156 |
|
157 |
|
158 |
-- |
159 |
|
160 |
*Sammy Pfeiffer* |
161 |
PhD Candidate at The Magic Lab within UTS. |