conditionally run "check ... scripts" tasks on travis?

Stream: general

[Scott Morrison]

Hi @Simon Hudon, I think the new travis tasks are slowing things down in an unfortunate way. Two of my PRs are at the moment sitting at yellow; travis has successfully checked all the proofs, but hasn't got around to spinning up the check install scripts tasks.

[Scott Morrison]

Is there some way we can only initiate them if something changed in the scripts directory?

[Scott Morrison]

The problem isn't that checking the install scripts is slow, but that travis is waiting to allocate a VM to check them in.

[Simon Hudon]

I think there are three things we can try here.

1. get Travis to not make redundant builds for PRs and pushes
2. collapse the four checks for scripts into 2 checks
3. disable those checks when the scripts don't change

[Simon Hudon]

I've talked to the Travis team about 1. and the change is in the pipeline

[Simon Hudon]

I can look into 2. tomorrow

[Simon Hudon]

I have no idea how to do 3. or if it's possible.

[Scott Morrison]

Great! No worries if it turns out to be too much work.

[Simon Hudon]

I think 1. will make a nice difference. Also, I've noticed today that Travis' workload was pretty heavy and it wasn't allocating many VMs for mathlib