Would it be an idea to add a make commando to run most off the tests that travis runs? Like the static tests and different board builts, or a sub set.
It would be great if this could be run from the RIOT root directory. :) Nick On 2 Mar 2016 11:59, "Francisco Javier Acosta Padilla" < francisco.aco...@inria.fr> wrote: > Hey! > > Some tears came out of my eyes when reading this message, I never gave any > thought to the T-guy, lots of pressure on him and nobody but you took care > of this… > > Thanks and next time we can try to be aware of this problem. > > Cheers! > > Paco. > > > On 2 March 2016 at 11:52:01, Oleg Hahm (oliver.h...@inria.fr) wrote: > > Hey Cenk! > > Thanks for this very important reminder! > > Cheers, > Oleg > > On Wed, Mar 02, 2016 at 07:59:36AM +0100, Cenk Gündogan wrote: > > Dear Developers, > > > > This is a friendly reminder that we should take more care > > of our travis backlog. > > > > Everytime a pull request gets rebased/squashed/new commits > > travis will enqueue a new task. This enqueing takes up space > > in the travis backlog and hinders us from getting quick feedback > > about important pull requests, which are basically ready to merge. > > > > I know that everyone loves to see her/his pull request checked > > by travis as soon as possible as means of a smoke test, > > but this "first check" can almost always be done by compiling locally! > > > > So please follow these two steps: > > 1) If your pull request has commits with a message > > that includes "SQUASH" or "FIXME" then travis will fail > > anyways. So why let it enqueue at the first place? > > Please use "[ci skip]" somewhere in your commit message > > if this is the case. Travis will ignore a pull request if the last > > commit > > message has "[ci skip]" somewhere in it. > > > > 2) (Maintainers only) If you notice several jobs in Travis for the same > > pull request, then please take the initiative and stop old jobs > > for obsolete commits. > > > > I also know that it's sometimes inevitable, especially when the pull > request > > was already squashed and is basically ready to merge, but another small > > remark forces us to commit/amend a change. (This often happens at > > hack'n'acks) > > If a maintainer is involved in this, then again, a pointer to 2), cancel > > jobs for obsolete commits. > > > > Take a glance at our current travis backlog [1]. The queue is still full > > from yesterday's > > hack'n'ack session, and that was about 8-9 hours ago. > > > > Develop cautiously! > > > > Cenk > > > > [1] https://travis-ci.org/RIOT-OS/RIOT/pull_requests > > _______________________________________________ > > devel mailing list > > devel@riot-os.org > > https://lists.riot-os.org/mailman/listinfo/devel > > -- > printk(KERN_DEBUG "%s: Done reprogramming Xilinx, %d bits, good > luck!\n",...); > linux-2.6.6/drivers/net/wan/lmc/lmc_main.c > ------------------------------ > _______________________________________________ > 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
