15:00:19 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:19 <zodbot> Meeting started Tue May  1 15:00:19 2018 UTC.  The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:19 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:19 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:00:19 <pwhalen> #chair pwhalen pbrobinson
15:00:19 <pwhalen> #topic roll call
15:00:19 <zodbot> Current chairs: pbrobinson pwhalen
15:00:25 <pwhalen> whos here today?
15:03:10 <jlinton_> Hi
15:03:29 <jlinton_> Was installing the 4.16.6 build...
15:04:07 <pwhalen> heya jlinton_
15:05:26 <pwhalen> jlinton_, did you have anything you wanted to discuss this week?
15:05:57 <jlinton_> Nothing I didn't mention on the fedora-arm channel
15:06:04 <jlinton_> other than FF 60 is broken too
15:07:10 <pwhalen> ugh, thanks for looking at it.
15:07:24 <jlinton_> i'm going to try building it with a slightly different set of flags (x28 exclusion, but its probably another black hole)
15:07:48 <jlinton_> At least for me debugging these firefox jit problems (cause it looks like its going into the jit around the crash at the moment)
15:07:52 <jlinton_> takes days..
15:08:17 <pwhalen> :(
15:08:46 <jlinton_> It actually tends to start, but then something is running which crashes
15:09:02 <pwhalen> well, I should keep you then :) .. lets cancel this meeting. I dont think anyone else going to make it
15:09:04 <jlinton_> and whatever it is, its not 100% reliably crashing, just about 90% of the time if I were guessing
15:10:08 <jlinton_> Sure
15:11:32 <pwhalen> sounds like it running a *little* better, when I filed the bug it pretty much opened and closed right away
15:12:01 <jlinton_> Well, its probably because my machine is 600Mhz.
15:12:09 <jlinton_> it just looks like its running longer
15:12:15 <pwhalen> heh, could be
15:12:46 <pwhalen> #info Meeting adjourned, no quorum.
15:12:51 <pwhalen> #endmeeting