Re: Travis build failure - fluke or broken builds? (PR #1755)

Hi Thomas,

On 01/10/14 07:36, Thomas Shinnick wrote:
> The most previous PR died with a broken build, saying
> (https://travis-ci.org/fontforge/fontforge/jobs/36532337#L8268)
> 
>         zeromq (libzmq) yes http://www.zeromq.org/
>         X Window System yes
>  
>    >>>  Error: inreplace failed
>    >>>  Makefile:
>    >>>    expected replacement of "ln -s /usr/local/bin/fontforge" with "ln -s
> $(bindir)/fontforge"
>         echo "brew build complete..."
>         brew build complete...
> 
> This would seem to correspond to this line in travis-scripts/fontforge.rb
> (https://github.com/fontforge/fontforge/blob/master/travis-scripts/fontforge.rb#L144)
> but I don't see any recent changes there.

That line looks like a work-around for a Travis issue. My guess is that issue as
been fixed and the build script needs the be changed.

> I'm not sure how to tell if my recent build for PR #1755 is actually the latest
> build attempted.  A useful coincidence is that I was working towards another PR,
> #1759, and I've just submitted that, which should test builds again.

The builds for pull requests are a little bit off the main line of Travis
builds. I always look at the Build History tab, which only shows the builds for
master, not the builds for pull requests.

>From the Build History, you can see that the difference between the last
successful build and the first failed build has nothing to do with that
fontforge.rb script. Hence my guess above.

(Incidentally, the builds for pull requests actually say they build on master,
it seems because they merge the PR into master behind the scenes before building)

> If that most definitely latest in-progress build fails
> (https://travis-ci.org/fontforge/fontforge/builds/36738686), can someone
> knowledgeable about Travis goodness look all this over?
> 
> 
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> 
> 
> 
> _______________________________________________
> fontforge-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fontforge-devel
> http://fontforge.10959.n7.nabble.com/Developer-f3.html
> 


-- 
Matijs

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html