Work with profiling groups in an AWS BugBust event (admin and player)

On an AWS BugBust event page, you can view the event's profiling groups, see how many are claimed and unclaimed, and see how many have been improved. On an event page, players can also claim profiling groups to work on. A player can claim up to three profiling groups at a time. A player can work on a profiling group until the state of the event is set to finalizing points. When an event's state is finalizing points, the event is over and players' scores and rankings are being calculated. For more information, see View the state of an AWS BugBust event and Scoring with Amazon CodeGuru Profiler performance improvements.

Find profiling groups in an AWS BugBust event (admin and player)

You can view your event's profiling groups on its event page. Your event page has profiling groups if its administrator imported profiling groups for players to work on. For more information, see Import performance issues from CodeGuru Profiler profiling groups.

View an event's imported profiling groups

1. If you are not on your event details page, follow the appropriate steps in View AWS BugBust event information (admin and player) to open it.

2. Choose Profiling groups.

An event can have more profiling groups than can appear in the event console page at a time. To find a profiling group you want to claim and work on, you can search for the following properties by entering a term in Find bugs.

• Profiling group – The name of the profiling group that contains the set of applications on which you want to work.

• Status – The status of the profiling group, which is claimed, unclaimed, checked-in, or evaluated.

• Points – The number of points that can be awarded when you check in code that improves the performance of the applications in a profiling group. For more information, see Scoring with Amazon CodeGuru Reviewer bug fixes.

You can also sort the profiling groups by how many points they are worth.

Evaluate a profiling group (admin)

The administrator evaluates an update to a profiling group that is submitted by a player. To submit the update, the player creates a pull request to check in their code, then notifies the administrator that their code is checked in. For more information, see Submit a profiling group improvement (player).

Evaluate a checked-in profiling group

1. If you are not on your event details page, follow the appropriate steps in View AWS BugBust event information (admin and player) to open it.

2. Choose Profiling groups.

3. If there are checked-in profiling groups in your event that have not been evaluated, choose Evalute n checked-in profiling groups, where n is the number of checked-in profiling groups that haven't been evaluated.

When the profiling groups are evaluated, CodeGuru Profiler determines how much more efficient their CPU usage is. Points are assigned based on the percent of improvement. When evaluation is complete, the status of the evaluated profiling groups updates to evaluated.

Setting the status of a profiling group (admin)

A profiling group can have one of four statuses.

• Unclaimed – An unclaimed profiling group is available for any player to claim and work on. After a profiling group is claimed, another player cannot claim it.

• Claimed – A claimed profiling group is claimed by an event player. Only that player can work on the profiling group and check in code to improve it.

• Checked-in – A checked-in profiling group has been checked in by the player who claimed it. A checked-in profiling group is ready for the admin to evaluate to determine how much the player's code improved the profiling group and then assign the appropriate points.

• Evaluated – An evaluated profiling group has been evaluated and points have been assigned based on how much more efficient the player's code made the profiling group. After the event has ended and all checked-in profiling groups have been evaluated, the event's status updates to closed.

An administrator can set the status of a profiling group from to claimed to unclaimed. If you set the status of a profiling group to unclaimed, then any player can claim that profiling group to improve it.

Change the status of a profiling group from claimed to unclaimed.

1. If you are not on your event details page, follow the appropriate steps in View AWS BugBust event information (admin and player) to open it.

2. Choose Profiling groups.

3. Select a profiling group. For information about finding a specific type of profiling group, see Find profiling groups in an AWS BugBust event (admin and player).

4. From the Mark as dropdown list, choose Mark as unclaimed.

Claim a profiling group (player)

You must claim a profiling group before you start working on improving it. When you claim a profiling group, no one else can claim the profiling group. You can claim up to three profiling groups at a time.

Claim a profiling group

1. If you are not on your event details page, follow the appropriate steps in View AWS BugBust event information (admin and player) to open it.

2. Choose Profiling groups.

3. Select a profiling group. For information about finding a specific type of profiling group, see Find bugs in an AWS BugBust event (admin and player). You can also choose Unclaimed profiling groups to view all profiling groups you can claim.

4. Choose Claim on a profiling group on which you want to work. When you do this, its status updates to claimed.

Submit a profiling group improvement (player)

After you are done writing code that improves a claimed profiling group, you submit it by creating a pull request in your code's repository. Next, you check it in from the AWS BugBust console. This notifies your event's administrator that it is ready to be evaluated. During evaluation of your code, the admin determines how much more efficient your code made the profiling group. The greater the improvement, the more points you earn. For more information, see Rules and scoring in AWS BugBust.

There is no time limit to improving a profiling group as long as it is submitted and checked in before its event ends.

Submit a profiling group improvement

1. Submit your updated code by creating a pull request in your code's repository.

2. If you are not on your event details page, follow the appropriate steps in View AWS BugBust event information (admin and player) to open it.

3. Choose Profiling groups.

4. Find the profiling group you want to check in. Only check in profiling groups for which you have submitted fixes.

5. On the profiling group, choose Check in.