NASA-AMMOS/aerie

Analyze scheduling fails after removing activity from plan

Closed this issue · 0 comments

Checked for duplicates

No - I haven't checked

Is this a regression?

Yes - This worked in a previous version

Version

2.21.0

Describe the bug

Running "analyze scheduling" after removing an activity from the plan results in an error.

Reproduction

  1. Run scheduling goals (goal I used is below)
  2. Delete some of the activity directives created by the scheduler
  3. Run "analyze" scheduling
  4. Fails with error (see log)

I used this scheduling goal:

export default (): Goal => {
    return Goal.ActivityRecurrenceGoal({ interval: Temporal.Duration.from({hours: 6}), activityTemplate:ActivityTemplates.AVS_BDS_or_EMEM_NAND_Power_Cycle({bds_emem: 'BOTH'})})
}

Logs

java.lang.NullPointerException: Cannot invoke "gov.nasa.jpl.aerie.scheduler.solver.ConflictSolverResult.satisfaction()" because "conflictSolverReturn" is null
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.satisfyGoalGeneral(PrioritySolver.java:507)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.satisfyGoal(PrioritySolver.java:329)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.solve(PrioritySolver.java:280)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.getNextSolution(PrioritySolver.java:190)
	at gov.nasa.jpl.aerie.scheduler.worker.services.SynchronousSchedulerAgent.schedule(SynchronousSchedulerAgent.java:238)
	at gov.nasa.jpl.aerie.scheduler.worker.SchedulerWorkerAppDriver.main(SchedulerWorkerAppDriver.java:105)

System Info

Chrome

Severity

Moderate