Phase out the old pulltester #4907

Now that Travis is working, in time we want to phase out the old pulltester (if only to stop all the email spam it generates...).

If desired this can be done partially first, ie disable the testing using ancient mingw 4.4 environment but keep the linux tests.

What are the blockers here?

cc: @theuni

Thanks, I meant to open a ticket for this last week.

I don't think there are any actual blockers left, other than the lack of downloads which is debatable. That functionality is coming to travis "at some point in the future".

The major difference once we shut down pull-tester is that people will quit getting nag mails from it. I'm sure several devs count on reading those mails as a way to see what's going on with PR's, but I don't think there's really any way to prepare for the change other than to issue a warning and flip the switch.

If it's actually desired to test an old gcc, we can just add a row to the travis build matrix. I'm not convinced there's a need, though. I'd rather see bleeding-edge compilers tested (so that we know what's coming), rather than crufty old ones.

@theuni No downloads is not a blocker for me - the current downloads, at least the windows ones, are useless in any case due to the old dev environment used. Having actually useful downloads in the future would with Travis would be useful.

I did notice the following:

• At the moment in Travis only x86/x86_64 linux execute the tests. The rest only does a build
• However in pulltester the tests are executed for windows as well using 'wine'

Can we get Travis to provide windows 32/64 bit test results using wine? (without a lot of extra work, like having to compile wine from scratch)

Ok, I've stopped the @BitcoinPullTester as travis has completely taken over its function. Long live pulltester, it worked well for 2+ years.

I think "well" is an overstatement. In any case, it is long since time that thing died. Does anyone else here a use for that server? Otherwise we should migrate what's left and turn it off.

On October 1, 2014 4:26:14 AM PDT, "Wladimir J. van der Laan" notifications@github.com wrote:

Ok, I've stopped the @BitcoinPullTester as travis has completely taken over its function. Long live pulltester, it worked well for 2+ years.

---

Reply to this email directly or view it on GitHub: #4907 (comment)

I just logged in to the pull-tester machine, nothing there I need. ACK from me on shutting it down.

Nothing that I need there either, ACK on shutting it down

Is there any plan to bring the qa/rpc-tests regression stuff into Travis? The pull-tester at least ran a few of them...

Also is it possible to get a notificytion via E-Mail from Travis if a build of an own pull is failing?

@ajweiss AFAIK Travis runs exactly the same tests as pull tester did.

@ajweiss as @laanwj said. See #4905 though, that's on my TODO. @Diapolo Looks like not yet, but soon. See https://github.com/travis-ci/travis-ci/issues/2128 .

@laanwj Done, you should close this issue.