Re: [riot-devel] Testing Task Force

2015-04-20 Thread Oleg Hahm
Hi!

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?)

Cheers,
Oleg
-- 
The problem with git jokes is everyone has their own version.


pgpc_ITvPLWSx.pgp
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Testing Task Force

2015-04-16 Thread Martine Lenders
Hi Oleg,

2015-04-16 9:36 GMT+02:00 Oleg Hahm oliver.h...@inria.fr:

 Hi!

  there were ~40 new builds opened yesterday [1]

 Sorry for the maybe stupid question, but how do zou see this? I find the
 Travis UI pretty confusing (and slow).


The date the build opened you sadly can't see, but I monitored
https://travis-ci.org/RIOT-OS/RIOT/pull_requests (I provided that link in
the reference) that day, that lists all incoming builds for PR (build on
push is disabled, so https://travis-ci.org/RIOT-OS/RIOT/builds only shows
older merges into master).

I concocted a little something yesterday night [1]. Maybe this will speed
things up a little.

Cheers,
Martine


[1] https://github.com/RIOT-OS/RIOT/pull/2822
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Testing Task Force

2015-04-15 Thread 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 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 [2].

Cheers,
Martine

[1] https://travis-ci.org/RIOT-OS/RIOT/pull_requests
[2] https://github.com/RIOT-OS/RIOT/pull/2793#issuecomment-92205543

2015-04-15 16:02 GMT+02:00 Oleg Hahm oliver.h...@inria.fr:

 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 jokes is that let understood = map (isJust .
 understand) $ repeat joke in or understood == False

 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


Re: [riot-devel] Testing Task Force

2015-04-15 Thread Philipp Rosenkranz
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 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.

Best,
Philipp

2015-04-15 17:32 GMT+02:00 Martine Lenders authmille...@gmail.com:

 Okay it takes ~1h to finish a build. My bad.

 2015-04-15 17:30 GMT+02:00 Martine Lenders authmille...@gmail.com:

 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 do that) kills jobs that are not current anymore (due to a PR
 being updated or force-pushed e.g.) as Kushal proposed in [2].

 Cheers,
 Martine

 [1] https://travis-ci.org/RIOT-OS/RIOT/pull_requests
 [2] https://github.com/RIOT-OS/RIOT/pull/2793#issuecomment-92205543

 2015-04-15 16:02 GMT+02:00 Oleg Hahm oliver.h...@inria.fr:

 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 jokes is that let understood = map (isJust .
 understand) $ repeat joke in or understood == False

 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel




 ___
 devel mailing list
 devel@riot-os.org
 https://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel