Hey folks from the testing task force,
does anyone know what exactly is currently wrong with Travis? I have the
impression that it didn't run a single test for RIOT today. E.g.
https://github.com/RIOT-OS/RIOT/pull/2764 is pending for 24h hours now.
there were ~40 new builds opened yesterday  and it takes travis ~30 min to finish a build (and since we are in the fair-use queue it works of the jobs more or less sequentially), so thats why the later ones are pending. I think we can speed up things a little if everyone (who has rights to do that) kills jobs that are not current anymore (due to a PR being updated or force-pushed e.g.) as Kushal proposed in .
Okay it takes ~1h to finish a build. My bad.
as Martine already remarked: in the worst case all our test jobs are
executed more or less sequentially. Given the fact that most test runs for
a single commit take about 60 min. to complete we can reach
a delay, between pushing a commit and the start of a test run, of about
1.5 days (on a more or less busy day)
BTW: We hope to have an implementation which can replace our current
travis setup by the end of the month. I am currently in the process of
looking into the source code of travis (it’s open-source after all) in order to
determine which components can be re-used for our purposes.
there were ~40 new builds opened yesterday 
Sorry for the maybe stupid question, but how do zou see this? I find the
Travis UI pretty confusing (and slow).
I realized that it is often the BUILDTEST_MCU_GROUP=cortex_m3_1 that run into
a timeout or other weird issues that can mostly be "solved" by restarting this
run. Any idea why this particular run seems to have resource problems? It's
not even the biggest group. (But maybe the one with least blacklisted tests?)