[haiku-development] Re: Failing unit tests
- From: "Mark Hellegers" <mark@xxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 25 May 2016 22:12:47 +0200 CEST
On Tue, May 24, 2016 at 11:36:49PM +0200, Mark Hellegers wrote:
We are trying to get things fixed as we go, but there has not
been
much
interest from the devs so far...
I would guess there would be no complaints if someone sets up the
build
bot to run the tests after each commit. That should be step one.
That will result in the buildbot doing a KDL on the first run, and
then
nothing will happen anymore. Either we must remove at least the KDLs
and
possibly all crashes from the tests, or we need to set things up in a
way that we can run the test harness on a non-Haiku host, that spawns
a
VM to run the tests, then collect the results (if possible, including
crashes and KDL reports)
Haha, yeah the KDL has to go first. Assuming it happens not just on my
machine. I created ticket #12798.
An alternative is collecting a list of KDL'ing tests and blacklisting
those until they are fixed.
So far I only got one and a couple of crashes. I will create tickets
for the crashes as well.
Blacklisting should work as well, but perhaps the most serious problems
will be fixed before we have a host running for the unit tests.
As for your problem with getting things written to disk, using 'sync'
may help a bit.
Thanks, I will give that a try. What I find strange, however, is that I
lost a few minutes of changes, not just a few seconds. Why were these
changes not written to disk?
Kind regards,
Mark Hellegers
--
Spangalese for beginners
'Bul esh na'
'How many ducks will you trade for my magic kidney stones'
Other related posts:
