Project

General

Profile

Actions
Copy link

Bug #3255

closed

error with migration test, not launched by default and should be sequential

Added by Vincent MEMBRÉ about 11 years ago. Updated about 11 years ago.

Status:
Released
Priority:
2
Assignee:
François ARMAND
Category:
Architecture - Dependencies
Target version:
2.6.0~beta1
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

migration tests are disabled by default, they are launched if the option -Dtest.progress=true is used.

That should be the opposite, the test should be run by default.

since migration to Scala2.10 (#3229), our migration tests does not pass anymore.

tests are launched concurrently, so sometimes the datas are deleted before being seen, we should use sequential test instead.

Actions
Copy link
 #1

Updated by François ARMAND about 11 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Anonymous about 11 years ago

Actions
Copy link
 #5

Updated by Jonathan CLARKE about 11 years ago

  • Status changed from Pending release to Released

This ticket has been addressed in version 2.6.0~beta1 of Rudder, which has just been released. Please see the changelog here: https://www.rudder-project.org/foswiki/System/Documentation:ChangeLog26.

Actions
Copy link

Also available in: Atom PDF