[SERVER-57158] selected_tests_gen fails when I run it in patch builds Created: 14/May/21 Updated: 29/Oct/23 Resolved: 26/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | DAG 2021-05-31 |
| Participants: | |
| Story Points: | 1 |
| Description |
Motivation for RequestI'd like to experiment with selected-tests to see how it reduces build times today. ContextI am looking into test selection mechanisms for test diagonalization DescriptionThis task fails with the following log. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] | |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! | |
| Comment by Githook User [ 26/May/21 ] | |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: | |
| Comment by David Bradford (Inactive) [ 26/May/21 ] | |
| Comment by David Bradford (Inactive) [ 21/May/21 ] | |
|
It looks like the last time the task was run was in this patch build on April 27 and it worked correctly. So it appears something has changed since then. | |
| Comment by David Bradford (Inactive) [ 21/May/21 ] | |
|
I added some extra debug info and tried a patch build. You can see the logs here. It looks like the issue the auth to selected-test-service is not working correctly, so calls to the service are getting redirected to okta login. So we need to figure out why the auth isn't working. | |
| Comment by David Bradford (Inactive) [ 17/May/21 ] | |
|
The new error should be investigated by DAG. | |
| Comment by Maria van Keulen [ 17/May/21 ] | |
|
As an update, I ran the task again as of the changes that fixed BF-21191, and the task failed with this message: | |
| Comment by David Bradford (Inactive) [ 17/May/21 ] | |
|
This looks like the failure is due to recent changes that STM has been making to the evergreen config.
|