API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Mar 20th, 2019
92
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.37 KB | None | 0 0
raw download clone embed print report
  1. [bvdirect@BVDirect-prod-web1 bvdirect]$ ./test-application.sh
  2. Running tests for the CoreBundle
  3. The CoreBundle did not encounter any issues during testing
  4. Running tests for the ApiBundle
  5. The ApiBundle did not encounter any issues during testing
  6. Running tests for the ScriptBundle/Command/Info
  7. The ScriptBundle/Command/Info had at least one issue while running PHPUnit
  8.  
  9. // Clearing the cache for the test environment with debug true
  10.  
  11. // Removing old cache directory...
  12.  
  13. // Finished
  14.  
  15. [OK] Cache for the "test" environment (debug=true) was successfully cleared.
  16.  
  17. PHPUnit 7.5.1 by Sebastian Bergmann and contributors.
  18.  
  19. .F..FFFF.F..................................................... 63 / 144 ( 43%)
  20. .........................S..................................... 126 / 144 ( 87%)
  21. .................. 144 / 144 (100%)
  22.  
  23. Time: 56.07 seconds, Memory: 64.25MB
  24.  
  25. There were 6 failures:
  26.  
  27. 1) Tests\ScriptBundle\Command\Info\CacheManagerTest::shouldDisplayMessageIfAllocationWasExceeded
  28. Failed asserting that '[03-15-2019 09:20:02] Starting Bvdirect Cache Manager.\n
  29. [03-15-2019 09:20:02] The command has begun checking ListingCacher statuses.\n
  30. [03-15-2019 09:20:03] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #1 has had its AmazonStatus changed from not-running to running.\n
  31. [03-15-2019 09:20:03] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #2 has had its AmazonStatus changed from not-running to running.\n
  32. [03-15-2019 09:20:03] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #1 has had its AlibrisStatus changed from not-running to running.\n
  33. [03-15-2019 09:20:03] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #2 has had its AlibrisStatus changed from not-running to running.\n
  34. [03-15-2019 09:20:03] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #1 has had its AbebooksStatus changed from not-running to running.\n
  35. [03-15-2019 09:20:03] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #2 has had its AbebooksStatus changed from not-running to running.\n
  36. [03-15-2019 09:20:03] The command has finished checking ListingCacher statuses.\n
  37. [03-15-2019 09:20:03] The command has begun checking ProductInfo statuses.\n
  38. [03-15-2019 09:20:03] Node ID #3 Products Cacher has become unavailable. All assigned requests have been unassigned.\n
  39. [03-15-2019 09:20:03] Node ID #4 Products Cacher has become unavailable. All assigned requests have been unassigned.\n
  40. [03-15-2019 09:20:03] The command has finished checking ProductInfo statuses.\n
  41. [03-15-2019 09:20:03] The command has begun distributing ISBNs to nodes.\n
  42. [03-15-2019 09:20:03] Allocating Application Priority slots for applications with ISBNs ready to cache.\n
  43. [03-15-2019 09:20:03] Node ID #1 has been reallocated 500 slots of Application Priority 1.\n
  44. [03-15-2019 09:20:03] Allocating Caching Priority slots for applications with ISBNs ready to cache.\n
  45. [03-15-2019 09:20:03] Node ID #1 has been allocated 25 ISBN slots of Caching Priority 1 for Application 2.\n
  46. [03-15-2019 09:20:03] Node ID #1 has been allocated 150 ISBN slots of Caching Priority 2 for Application 2.\n
  47. [03-15-2019 09:20:03] Node ID #1 has been allocated 125 ISBN slots of Caching Priority 3 for Application 2.\n
  48. [03-15-2019 09:20:03] Node ID #1 has been allocated 154 ISBN slots of Caching Priority 4 for Application 2.\n
  49. [03-15-2019 09:20:03] Node ID #1 has unused slots of Caching Priority 1 for Application 2. Unsused slots will be reallocated.\n
  50. [03-15-2019 09:20:03] Node ID #1 has unused slots of Caching Priority 2 for Application 2. Unsused slots will be reallocated.\n
  51. [03-15-2019 09:20:03] Node ID #1 has unused slots of Caching Priority 3 for Application 2. Unsused slots will be reallocated.\n
  52. [03-15-2019 09:20:03] Node ID #1 has unused slots of Caching Priority 4 for Application 2. Unsused slots will be reallocated.\n
  53. [03-15-2019 09:20:03] Node ID #1 contains 354 slots available for redistribution. These slots will be divided amongst Caching Priorities that have reached their cap.\n
  54. [03-15-2019 09:20:03] There are no remaining ISBNs to assign for remaining application slots.\n
  55. [03-15-2019 09:20:03] Node ID #1 has been assigned 100 ISBNs of Caching Priority 4 for Application 2.\n
  56. [03-15-2019 09:20:03] The status for CacherApiProcess #4 has been updated to in_process.\n
  57. [03-15-2019 09:20:03] The command has finished distributing isbns to nodes.\n
  58. [03-15-2019 09:20:03] The command has begun checking the API Process statuses.\n
  59. [03-15-2019 09:20:03] The command has marked API Process 2 as ready.\n
  60. [03-15-2019 09:20:03] The command has marked API Process 3 as ready.\n
  61. [03-15-2019 09:20:03] The command has marked API Process 6 as ready.\n
  62. [03-15-2019 09:20:03] The command has marked API Process 9 as ready.\n
  63. [03-15-2019 09:20:03] The command has marked API Process 10 as ready.\n
  64. [03-15-2019 09:20:03] The command has marked API Process 11 as ready.\n
  65. [03-15-2019 09:20:03] The command has finished checking the API Process statuses.\n
  66. [03-15-2019 09:20:03] Bvdirect Cache Manager has finished working and will now exit.\n
  67. ' contains "Node ID #1 is currently exceeding its capacity for Caching Priority 4 by 6 slots, the command will attempt to redistribute ISBNs to this node during redistribution if there are remaining slots.".
  68.  
  69. /var/www/html/bvdirect/tests/ScriptBundle/Command/Info/CacheManagerTest.php:105
  70.  
  71. 2) Tests\ScriptBundle\Command\Info\CacheManagerTest::shouldDivideRemainingCapSpaceToPrioritiesThatHaveReachedTheirCap
  72. Failed asserting that 100 matches expected 19.
  73.  
  74. /var/www/html/bvdirect/tests/ScriptBundle/Command/Info/CacheManagerTest.php:188
  75.  
  76. 3) Tests\ScriptBundle\Command\Info\CacheManagerTest::shouldDistributeIsbnsEvenlyAmongApplications
  77. Failed asserting that 250 matches expected 50.
  78.  
  79. /var/www/html/bvdirect/tests/ScriptBundle/Command/Info/CacheManagerTest.php:249
  80.  
  81. 4) Tests\ScriptBundle\Command\Info\CacheManagerTest::shouldDistributeIsbnsByApplicationPriority
  82. Failed asserting that 20 matches expected 10.
  83.  
  84. /var/www/html/bvdirect/tests/ScriptBundle/Command/Info/CacheManagerTest.php:319
  85.  
  86. 5) Tests\ScriptBundle\Command\Info\CacheManagerTest::shouldDistributeIsbnsEvenlyWithSameApplicationPriority
  87. Failed asserting that 50 matches expected 25.
  88.  
  89. /var/www/html/bvdirect/tests/ScriptBundle/Command/Info/CacheManagerTest.php:401
  90.  
  91. 6) Tests\ScriptBundle\Command\Info\CacheManagerTest::shouldNotUpdateStatusForCacherApiProcess
  92. Failed asserting that '[03-15-2019 09:20:13] Starting Bvdirect Cache Manager.\n
  93. [03-15-2019 09:20:13] The command has begun checking ListingCacher statuses.\n
  94. [03-15-2019 09:20:13] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #1 has had its AmazonStatus changed from not-running to running.\n
  95. [03-15-2019 09:20:13] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #2 has had its AmazonStatus changed from not-running to running.\n
  96. [03-15-2019 09:20:13] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #1 has had its AlibrisStatus changed from not-running to running.\n
  97. [03-15-2019 09:20:13] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #2 has had its AlibrisStatus changed from not-running to running.\n
  98. [03-15-2019 09:20:13] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #1 has had its AbebooksStatus changed from not-running to running.\n
  99. [03-15-2019 09:20:13] An email would have been sent to bvmonitor@woboinc.com with the contents Node ID #2 has had its AbebooksStatus changed from not-running to running.\n
  100. [03-15-2019 09:20:13] The command has finished checking ListingCacher statuses.\n
  101. [03-15-2019 09:20:13] The command has begun checking ProductInfo statuses.\n
  102. [03-15-2019 09:20:13] Node ID #3 Products Cacher has become unavailable. All assigned requests have been unassigned.\n
  103. [03-15-2019 09:20:13] Node ID #4 Products Cacher has become unavailable. All assigned requests have been unassigned.\n
  104. [03-15-2019 09:20:13] The command has finished checking ProductInfo statuses.\n
  105. [03-15-2019 09:20:13] The command has begun distributing ISBNs to nodes.\n
  106. [03-15-2019 09:20:13] Allocating Application Priority slots for applications with ISBNs ready to cache.\n
  107. [03-15-2019 09:20:13] Node ID #1 has been reallocated 500 slots of Application Priority 1.\n
  108. [03-15-2019 09:20:13] Allocating Caching Priority slots for applications with ISBNs ready to cache.\n
  109. [03-15-2019 09:20:13] Node ID #1 has been allocated 25 ISBN slots of Caching Priority 1 for Application 1.\n
  110. [03-15-2019 09:20:13] Node ID #1 has been allocated 150 ISBN slots of Caching Priority 2 for Application 1.\n
  111. [03-15-2019 09:20:13] Node ID #1 has been allocated 125 ISBN slots of Caching Priority 3 for Application 1.\n
  112. [03-15-2019 09:20:13] Node ID #1 has been allocated 200 ISBN slots of Caching Priority 4 for Application 1.\n
  113. [03-15-2019 09:20:13] Node ID #1 has unused slots of Caching Priority 1 for Application 1. Unsused slots will be reallocated.\n
  114. [03-15-2019 09:20:13] Node ID #1 has unused slots of Caching Priority 2 for Application 1. Unsused slots will be reallocated.\n
  115. [03-15-2019 09:20:13] Node ID #1 has unused slots of Caching Priority 4 for Application 1. Unsused slots will be reallocated.\n
  116. [03-15-2019 09:20:13] Node ID #1 does not contain 375 slots available for redistribution. These slots will be divided amongst Caching Priorities that have reached their cap.\n
  117. [03-15-2019 09:20:13] Node ID #1 has been reallocated 500 ISBN slots of Caching Priority 3 for Application 1.\n
  118. [03-15-2019 09:20:13] Node ID #1 has been assigned 300 ISBNs of Caching Priority 3 for Application 1.\n
  119. [03-15-2019 09:20:13] The status for CacherApiProcess #2 has been updated to in_process.\n
  120. [03-15-2019 09:20:13] The status for CacherApiProcess #4 has been updated to in_process.\n
  121. [03-15-2019 09:20:13] The status for CacherApiProcess #6 has been updated to in_process.\n
  122. [03-15-2019 09:20:13] The command has finished distributing isbns to nodes.\n
  123. [03-15-2019 09:20:13] The command has begun checking the API Process statuses.\n
  124. [03-15-2019 09:20:14] The command has marked API Process 3 as ready.\n
  125. [03-15-2019 09:20:14] The command has marked API Process 9 as ready.\n
  126. [03-15-2019 09:20:14] The command has marked API Process 10 as ready.\n
  127. [03-15-2019 09:20:14] The command has marked API Process 11 as ready.\n
  128. [03-15-2019 09:20:14] The command has finished checking the API Process statuses.\n
  129. [03-15-2019 09:20:14] Bvdirect Cache Manager has finished working and will now exit.\n
  130. ' does not contain "The status for CacherApiProcess #6 has been updated to in_process.".
  131.  
  132. /var/www/html/bvdirect/tests/ScriptBundle/Command/Info/CacheManagerTest.php:474
  133.  
  134. FAILURES!
  135. Tests: 144, Assertions: 317, Failures: 6, Skipped: 1.
  136. Running tests for the ScriptBundle/Command/Maintenance
  137. The ScriptBundle/Command/Maintenance did not encounter any issues during testing
  138. Running tests for the ScriptBundle/Command/Order
  139. The ScriptBundle/Command/Order did not encounter any issues during testing
  140. Running tests for the ScriptBundle/Monitor
  141. The ScriptBundle/Monitor did not encounter any issues during testing
  142. Running tests for the ScriptBundle/Util
  143. The ScriptBundle/Util did not encounter any issues during testing
  144. Running tests for the ScriptBundle/Services
  145. The ScriptBundle/Services did not encounter any issues during testing
  146. Running tests for the UserBundle
  147. The UserBundle did not encounter any issues during testing
  148. At least one test encountered a problem.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!