Sorry for the error spam, had to fix one erroneous check (that forced exiting
with errorlevel 0 instead of the proper one).
- Original message -
From: build...@reactos.org
To: cae...@myopera.com
Date: Tue, 06 Mar 2012 21:18:43 +
Subject: buildbot failure in ReactOS on Windows_AMD64_1
It seems that any crash in APITESTS on vbox testbot is causing
rosautotest to redo from start. We can see this in stdio log:
http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/6323/steps/test/logs/stdio
(just search for "restarting" word). APITESTS are repated and such log
as a wh
Guys, this is serious, crash is still present. Without test coverage we
risk slipping regressions in and KVM testbot does not cover ahk app
tests.
--
With best regards
Caemyr
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/l
This one is caused by rev 57225:
Backtrace:
http://www.reactos.org/paste/index.php/10472/
Please fix
- Original message -
From: build...@reactos.org
To: cae...@myopera.com
Subject: buildbot failure in ReactOS on Windows_AMD64_1 VBox-Test
Date: Sun, 02 Sep 2012 22:50:06 +
The Buildbo
Test run failed due to exceeding the maximum number of restarts, Problem
started with unexpected crash:
Running Wine Test, Module: pdh, Test: pdh
Assertion 'KiTimerTableListHead[Index].Time.QuadPart <=
Timer->DueTime.QuadPart' failed at ../../ntoskrnl/ke/dpc.c line 252
[7h
Entered debugger on em
@Giannis - as you required:
http://svn.reactos.org/svn/reactos?view=revision&revision=57330
This commit is causing the following crash in user32_apitest:desktop
(reported in CORE-6682
desktop.c:83: Test failed: 3: expected error 0xc142 in child process
got 0x0
(../../win32ss/user/ntuser/desk
Hi,
Le mardi 14 août 2012 à 02:48 +0200, cae...@myopera.com a écrit :
> Rosautotest, strangely, is affected only on vbox, on kvm the apitest
> crash is not causing a restart of test run. Winetests, if i recall
> correctly, were never affected in such way.
Nope. KVM exposes the same issue. Well, a
On Tue, Aug 14, 2012, at 08:02 AM, Pierre Schweitzer wrote:
> Nope. KVM exposes the same issue. Well, at least, randomly.
Are you sure? I never seen KVM failing on test log upload.
> It has. This prevents for storing partial runs, or not consistant runs.
> Furthermore, I'm against hacking testman
cae...@myopera.com wrote:
It seems that any crash in APITESTS on vbox testbot is causing
rosautotest to redo from start.
Apparently, we're dealing with lost cache contents or even filesystem
corruption here. If you look for "Writing initial journal file", you'll
see that it appears multiple t
Colin Finck wrote:
If somebody has a few minutes to spend, please take a look at
CJournaledTestList.cpp in rosautotest.
I've added flags to bypass caches in r57077, but this doesn't fix the
problem unfortunately. I'm not sure whether any other (proper) fix is
even doable in rosautotest itsel
This issue comes and goes, from what i noticed its triggered by any
crash in APITESTS. Crashes in WINETESTS are not triggereing it.
On Tue, Aug 14, 2012, at 11:28 PM, Colin Finck wrote:
> I've added flags to bypass caches in r57077, but this doesn't fix the
> problem unfortunately. I'm not sure
Hi,
I'm really sorry about the inconvenience. When I committed the test case I
didn't expect it would cause such great problems and thought that testbot would
continue gratefully. So I deactivated the tests till either it doesn't crash in
the kernel or the test process is more solid.
Now that
12 matches
Mail list logo
