From 365d0bccd577f1a30dd7cc1ad0c9f03386605acb Mon Sep 17 00:00:00 2001
From: Norman Feske <norman.feske@genode-labs.com>
Date: Fri, 22 Jun 2018 10:44:00 +0200
Subject: [PATCH] init.run: prioritize timer over test

The 200-second timeout of the init test triggers on some test platform
(in particular on qemu) while it is overly pessimistic on others.
This patch aims at stabilizing the timing behavior of the test across
the tested kernels/machines.
---
 repos/os/run/init.run | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/repos/os/run/init.run b/repos/os/run/init.run
index bd43a9fb64..31837bf22f 100644
--- a/repos/os/run/init.run
+++ b/repos/os/run/init.run
@@ -13,7 +13,7 @@ create_boot_directory
 #
 
 append config {
-<config>
+<config prio_levels="2">
 	<parent-provides>
 		<service name="ROM"/>
 		<service name="CPU"/>
@@ -35,7 +35,7 @@ append config {
 		<provides><service name="Timer"/></provides>
 	</start>
 
-	<start name="report_rom">
+	<start name="report_rom" priority="-1">
 		<resource name="RAM" quantum="2M"/>
 		<provides> <service name="ROM"/> <service name="Report"/> </provides>
 		<config verbose="no">
@@ -44,7 +44,7 @@ append config {
 		</config>
 	</start>
 
-	<start name="test-init">
+	<start name="test-init" priority="-1">
 		<resource name="RAM" quantum="4M"/>
 		<provides> <service name="LOG"/> </provides>
 		<config>
@@ -1518,7 +1518,7 @@ append config {
 		</route>
 	</start>
 
-	<start name="init" caps="2000">
+	<start name="init" caps="2000" priority="-1">
 		<binary name="init"/>
 		<resource name="RAM" quantum="16M"/>
 		<configfile name="init.config"/>