testsuites/validation/tc-scheduler-remove-processor.c

1 files changed, 9 insertions, 2 deletions

diff --git a/testsuites/validation/tc-scheduler-remove-processor.c b/testsuites/validation/tc-scheduler-remove-processor.c
index e9967cb35a..14e3ad89c2 100644
--- a/testsuites/validation/tc-scheduler-remove-processor.c
+++ b/testsuites/validation/tc-scheduler-remove-processor.c
@@ -246,7 +246,7 @@ typedef struct {
   /**
    * @brief This member provides the scheduler operation records.
    */
-  T_scheduler_log_10 scheduler_log;;
+  T_scheduler_log_4 scheduler_log;;
 
   /**
    * @brief This member contains the return value of the
@@ -363,7 +363,7 @@ static void DoRemoveProcessor( Context *ctx )
 {
   T_scheduler_log *log;
 
-  log = T_scheduler_record_10( &ctx->scheduler_log );
+  log = T_scheduler_record_4( &ctx->scheduler_log );
   T_null( log );
 
   ctx->status = rtems_scheduler_remove_processor( ctx->id, ctx->cpu_index );
@@ -890,6 +890,13 @@ static void RtemsSchedulerReqRemoveProcessor_Post_Removed_Check(
        * rtems_scheduler_remove_processor() call.
        */
       if ( ctx->home && ctx->helping ) {
+        /*
+         * For these test scenarios we use scheduler A in which the runner
+         * remains scheduled.  So, an ask for help request is issued, when the
+         * processor allocated to a task which uses the scheduler as a helping
+         * scheduler is removed.
+         */
+        T_eq_u32( ctx->id, SCHEDULER_A_ID );
         T_eq_sz( ctx->scheduler_log.header.recorded, 3 );
         T_eq_int(
           ctx->scheduler_log.events[ 0 ].operation,