<div dir="auto">This failure is not directly related to an opensmalltalk change.<div dir="auto">It is either a CI infrastructure problem, or an ubuntu upgrade problem.</div><div dir="auto">This is hell. We are good enough at producing our own bugs and don't need any help for that...</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le dim. 13 oct. 2019 à 22:14, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Thank you Phil. Yes that is exactly what I was worried about. I'll<br>
stop worrying now :-)<br>
<br>
Dave<br>
<br>
On Sun, Oct 13, 2019 at 04:13:03PM -0400, Phil B wrote:<br>
> <br>
> I just realized that you might have known that but might have been rather<br>
> asking if *your* particular changes are what broke it. I'd guess is<br>
> probably not since your changes don't appear to break anything new per<br>
> <a href="https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds" rel="noreferrer noreferrer" target="_blank">https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds</a>. (i.e. the same<br>
> configurations were broken before and after your push) Unfortunately, all<br>
> you can do is guess when the build was broken before and after a push<br>
> (which arguably defeats the purpose/value of CI) since it's *possible* that<br>
> when whatever was broken gets fixed, it might reveal a problem with your<br>
> changes.<br>
> <br>
> On Sun, Oct 13, 2019 at 2:41 PM Phil B <<a href="mailto:pbpublist@gmail.com" target="_blank" rel="noreferrer">pbpublist@gmail.com</a>> wrote:<br>
> <br>
> > That's the 'continuous' part of continuous integration: when you push, it<br>
> > builds.<br>
> ><br>
> > On Sun, Oct 13, 2019 at 2:07 PM David T. Lewis <<a href="mailto:lewis@mail.msen.com" target="_blank" rel="noreferrer">lewis@mail.msen.com</a>><br>
> > wrote:<br>
> ><br>
> >><br>
> >> Forgive the newbie question, but I pushed this to a branch, not expecting<br>
> >> that it would kick off a Travis build. Did I break something?<br>
> >><br>
> >> Thanks,<br>
> >> Dave<br>
> >><br>
> >><br>
> >> On Sun, Oct 13, 2019 at 06:02:20PM +0000, Travis CI wrote:<br>
> >> ><br>
> >> > Build Update for OpenSmalltalk/opensmalltalk-vm<br>
> >> > -------------------------------------<br>
> >> ><br>
> >> > Build: #1818<br>
> >> > Status: Errored<br>
> >> ><br>
> >> > Duration: 9 mins and 17 secs<br>
> >> > Commit: c7171f4 (dtl/vm-module-load-error-messages)<br>
> >> > Author: David T. Lewis<br>
> >> > Message: Ensure readable error message for VM module dlopen failures.<br>
> >> > If a module such as vm-display-X11 fails to load due to dynamic linking<br>
> >> > errors such as symbol not found or missing runtime libary on the target<br>
> >> > machine, then provide a meaningful error message.<br>
> >> > Eliminate unnecessary check for if (strstr(why,"undefined symbol"))<br>
> >> {...}<br>
> >> > because it eats errors, e.g. in the case of missing xRender runtime<br>
> >> > and VM compiled with xRender dev libaries.<br>
> >> > Improve the error message for readability. Add fflush() for stderr<br>
> >> > output to prevent messages being lost or mixed with stdout. Remove<br>
> >> > redundant and unreachable code.<br>
> >> ><br>
> >> > Note, duplicate error messages on for load failures may occur due<br>
> >> > to path setup issues in the /bin/squeak start script, are are not<br>
> >> > a VM issue per se.<br>
> >> ><br>
> >> > Example error message for VM compiled with xRender library for large<br>
> >> > cursor support, and run on a machine with missing runtime library:<br>
> >> ><br>
> >> > vm-display-X11 tryLoading<br>
> >> /usr/local/lib/squeak/5.0-201910110209/vm-display-X11.so: dlopen:<br>
> >> libXrender.so.1: cannot open shared object file: No such file or directory<br>
> >> ><br>
> >> > View the changeset:<br>
> >> <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/c7171f4ac443" rel="noreferrer noreferrer" target="_blank">https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/c7171f4ac443</a><br>
> >> ><br>
> >> > View the full build log and details:<br>
> >> <a href="https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/597321212?utm_medium=notification&utm_source=email" rel="noreferrer noreferrer" target="_blank">https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/597321212?utm_medium=notification&utm_source=email</a><br>
> >> ><br>
> >> > --<br>
> >> ><br>
> >> > You can unsubscribe from build emails from the<br>
> >> OpenSmalltalk/opensmalltalk-vm repository going to<br>
> >> <a href="https://travis-ci.org/account/preferences/unsubscribe?repository=8795279&utm_medium=notification&utm_source=email" rel="noreferrer noreferrer" target="_blank">https://travis-ci.org/account/preferences/unsubscribe?repository=8795279&utm_medium=notification&utm_source=email</a><br>
> >> .<br>
> >> > Or unsubscribe from *all* email updating your settings at<br>
> >> <a href="https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email" rel="noreferrer noreferrer" target="_blank">https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email</a><br>
> >> .<br>
> >> > Or configure specific recipients for build notifications in your<br>
> >> .travis.yml file. See <a href="https://docs.travis-ci.com/user/notifications" rel="noreferrer noreferrer" target="_blank">https://docs.travis-ci.com/user/notifications</a>.<br>
> >> ><br>
> >><br>
> >><br>
<br>
</blockquote></div>