<    April 2017    >
Su Mo Tu We Th Fr Sa  
                   1  
 2  3  4  5  6  7  8  
 9 10 11 12 13 14 15  
16 17 18 19 20 21 22  
23 24 25 26 27 28 29  
30
02:41 kingarmadillo joined
03:20 jamesmillerio joined
04:37 dre^ joined
04:52 austin987 joined
04:53 mikeliss joined
05:51 lpin joined
06:27 rickmak_ joined
06:52 rickmak joined
06:55 rickmak_ joined
07:13 mtodor joined
07:23 zupo joined
07:26 basro_ joined
07:45 kingarmadillo joined
07:58 ssbarnea joined
08:28 notebox joined
08:30 kingarmadillo joined
09:03 rickmak_ joined
09:47 ssbarnea joined
10:17 Disconsented joined
10:23 jantman joined
10:49 rickmak joined
11:03 kingarmadillo joined
11:43 zupo joined
11:51 notebox joined
12:13 moongazer joined
12:14 moongazer joined
12:16 moongazer joined
12:17 moongazer joined
12:24 moongazer joined
12:25 moongazer joined
12:32 kingarmadillo joined
12:45 jamesmillerio joined
13:08 Sound joined
13:10 jeffreylevesque joined
13:16 mtodor joined
13:29 jeffreylevesque joined
13:33 jugglinmike joined
13:36 <matthiaskrgr> hi, I have a travis.yml that runs program --arg="foo : bar" and the colon seems to break the syntax of the entire travis file
13:38 <matthiaskrgr> the program is called via
13:38 <matthiaskrgr> --template='{callstack}: ({severity}) {message} [{id}]'
13:38 <matthiaskrgr> which blows up everything
13:38 <matthiaskrgr> as soon as I remove the":", at least the travis cfg linter no longer complains
13:39 <matthiaskrgr> it is kind of strange because I tell it that it is just a string by having the quotation marks. so why does it look for syntax errors inside strings ...
13:44 jamesmillerio joined
13:52 <mtodor> @matthiaskrgr it would be better if you can provide link to travis.yml file, but it could be something with yaml parsing - maybe you can try to encapsulate full command: 'program --arg="foo : bar"'
13:52 <mtodor> you can also check your file here: http://lint.travis-ci.org/
14:11 moongazer joined
14:26 notebox joined
14:52 GitHub143 joined
14:52 <GitHub143> [travis-ruby-client] rkh pushed 1 new commit to master: https://git.io/vSzUb
14:52 <GitHub143> travis-ruby-client/master d4a2be8 Konstantin Haase: regenerate structure for yardoc
14:52 GitHub143 left
15:00 lem-fr joined
15:55 mikeliss joined
15:58 lsmith joined
16:22 cmos joined
16:24 <cmos> any ideas why two builds for the same commit would have different results?
16:24 <cmos> in particular, the original commit passed, then I tagged it as a new release, and the release build failed
16:25 <cmos> see https://travis-ci.org/julian-wolf/EasyPhys.jl/builds/218239415 vs https://travis-ci.org/julian-wolf/EasyPhys.jl/builds/218234918
17:36 <BtbN> Have you tried just re-running it?
17:40 <cmos> BtbN: I hadn't; am doing so presently
17:41 <cmos> if this fixes it, awesome! it's still be nice to know why this would happen, though
17:41 <BtbN> it probably downloads stuff from all over the net
17:41 <BtbN> one of those servers has a hickup, and it fails
17:46 ssbarnea joined
18:03 zupo joined
18:23 notebox joined
18:52 Diggsey joined
19:32 kingarmadillo joined
19:53 davehunt joined
20:07 jamesmillerio joined
21:49 VladGh joined
21:57 dave0x6d joined
22:02 <jugglinmike> Does anyone here know how the `TRAVIS_COMMIT_RANGE` variable is calculated?
22:02 <jugglinmike> Or maybe where I might find the relevant source?
22:05 <jugglinmike> Well here's a start https://github.com/travis-ci/travis-build/blob/0dcba7c2bc4fea666d727fe545a172a261a16336/lib/travis/build/env/builtin.rb#L44
22:11 <jugglinmike> I'm having trouble tracing that value.
22:12 <jugglinmike> I think I found a bug, though. If anyone on the Travis team is out there, this build seems wrong: https://travis-ci.org/w3c/web-platform-tests/builds/219056744
22:50 ssbarnea joined
23:04 ssbarnea joined
23:14 ssbarnea joined
23:28 ssbarnea joined
23:29 TheJJ joined
23:29 ski7777 joined
23:55 ssbarnea joined