Dear RIOTers,
I just read about a buffer overflow in X.Org caused by a macro in a header
file [1]. While the bug was fixed in 2013 it still may cause bugs in other
software that uses this macro and has not been recompiled.
If we envision that single libraries may be updated in future IoT scenario
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.
Cheers,
Oleg
--
The bad thing about Haskell jok
Hi,
there were ~40 new builds opened yesterday [1] 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 d
Okay it takes ~1h to finish a build. My bad.
2015-04-15 17:30 GMT+02:00 Martine Lenders :
> Hi,
> there were ~40 new builds opened yesterday [1] 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
Hi,
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 mor
