Project

General

Profile

Bug #5064

Ошибка в чекере при удалении требования

Added by Viktoria Kopach over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
07/14/2014
Due date:
% Done:

100%

Estimated time:
Detected in build:
0.16.201
Platform:
Linux x86
Published in build:
0.16.202

Description

Используется Eclipse Luna 4.4.
Проект прилагаю. Случается при удалении требования 01.

Error
Mon Jul 14 16:49:00 MSK 2014
Errors running builder 'Requality Checkers' on project 'Project04'.

java.lang.RuntimeException: node not found: 6a4f2357-5b56-4350-9b8b-5f8ed48ce06d
at com.unitesk.requality.core.TreeDB.getNode(TreeDB.java:384)
at com.unitesk.requality.eclipse.core.TreesTracker.getNodeByResource(TreesTracker.java:500)
at com.unitesk.requality.eclipse.core.EclipseChecker$1.visit(EclipseChecker.java:32)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:56)
at com.unitesk.requality.eclipse.core.EclipseChecker.build(EclipseChecker.java:62)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:733)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)


Files

Project04.zip (28.9 KB) Project04.zip Viktoria Kopach, 07/14/2014 04:58 PM

Associated revisions

Revision 3637 (diff)
Added by Denis Kildishev over 5 years ago

fixes: #5064; when node is not exists getNodeByResource tries to call db.getNode that causes runtime exeption instead of return of null value. new behaviour of getNodeByResource returns null when db.getNode could not found related node. Behaviour of EclipseChecker is already handles null as result for getNodeByResource as "node not found" situation.

Revision 668e65ca (diff)
Added by Denis Kildishev over 5 years ago

fixes: #5064; when node is not exists getNodeByResource tries to call db.getNode that causes runtime exeption instead of return of null value. new behaviour of getNodeByResource returns null when db.getNode could not found related node. Behaviour of EclipseChecker is already handles null as result for getNodeByResource as "node not found" situation.

git-svn-id: https://forge.ispras.ru/svn/reqdb/trunk/requality@3637 f558eac1-05b1-4da7-9ed5-5050e8a619d6

Revision 3637 (diff)
Added by Denis Kildishev over 5 years ago

fixes: #5064; when node is not exists getNodeByResource tries to call db.getNode that causes runtime exeption instead of return of null value. new behaviour of getNodeByResource returns null when db.getNode could not found related node. Behaviour of EclipseChecker is already handles null as result for getNodeByResource as "node not found" situation.

History

#1

Updated by Denis Kildishev over 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset r3637.

#2

Updated by Alexey Khoroshilov over 5 years ago

  • Target version set to 0.16
  • Published in build set to 0.16.202
#3

Updated by Viktoria Kopach over 5 years ago

  • Status changed from Resolved to Verified
#4

Updated by Alexey Khoroshilov over 4 years ago

  • Status changed from Verified to Closed

Also available in: Atom PDF