[jira] [Assigned] (ACCUMULO-4833) Replication randomwalk test is broken/misplaced
[ https://issues.apache.org/jira/browse/ACCUMULO-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Miller reassigned ACCUMULO-4833: Assignee: Michael Miller > Replication randomwalk test is broken/misplaced > --- > > Key: ACCUMULO-4833 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4833 > Project: Accumulo > Issue Type: Bug > Components: test >Affects Versions: 1.7.4, 1.9.0 >Reporter: Michael Miller >Assignee: Michael Miller >Priority: Minor > > While trying to run the Randomwalk Concurrent test, it will consistently > error out and stop due to the Replication test. This test doesn't take in > consideration the randomwalk state and simply just waits 30s and fails if the > data is not replicated. Maybe the test could be rewritten to handle the > state of replication better or it should be moved outside of randomwalk. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r174223864 ## File path: contributor/making-release.md ## @@ -22,6 +22,14 @@ There are number of things that are required before attempting to build a releas Given all of this, it's recommended that you only attempt making a release from a GNU/Linux machine. +## Triage issues. + +Before creating a release candidate, all open issues with a fix version of the +release candidate should be triaged. During the transition from JIRA to GitHub +issues, anyone doing triage will need to search for open issues in both +locations. Searching in both locations is only necessary for branches that +have not released since the transition started. Review comment: Ok, thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] keith-turner commented on a change in pull request #59: proposal for github issues
keith-turner commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r174213824 ## File path: contributor/making-release.md ## @@ -22,6 +22,14 @@ There are number of things that are required before attempting to build a releas Given all of this, it's recommended that you only attempt making a release from a GNU/Linux machine. +## Triage issues. + +Before creating a release candidate, all open issues with a fix version of the +release candidate should be triaged. During the transition from JIRA to GitHub +issues, anyone doing triage will need to search for open issues in both +locations. Searching in both locations is only necessary for branches that +have not released since the transition started. Review comment: Yes, in 5b0d6c4 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] joshelser commented on a change in pull request #59: proposal for github issues
joshelser commented on a change in pull request #59: proposal for github issues URL: https://github.com/apache/accumulo-website/pull/59#discussion_r174213350 ## File path: contributor/making-release.md ## @@ -22,6 +22,14 @@ There are number of things that are required before attempting to build a releas Given all of this, it's recommended that you only attempt making a release from a GNU/Linux machine. +## Triage issues. + +Before creating a release candidate, all open issues with a fix version of the +release candidate should be triaged. During the transition from JIRA to GitHub +issues, anyone doing triage will need to search for open issues in both +locations. Searching in both locations is only necessary for branches that +have not released since the transition started. Review comment: > Yes, I think it would be best to move the info in contrib.md to the website and mention that the labels only apply to the main repo. Could remove the info from contrib.md. Did this happen? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
