[SERVER-35250] save dbtest debug symbols in debug_symbols tar Created: 25/May/18 Updated: 29/Oct/23 Resolved: 10/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.5, 4.1.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Jonathan Abrahams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-qwin-eligible | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||||||
| Sprint: | TIG 2018-08-27 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 15 | ||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
|
I would like to be able to symbolize stack traces generated by dbtest in BF's. |
| Comments |
| Comment by Githook User [ 21/Nov/18 ] |
|
Author: {'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com', 'username': 'hptabster'}Message: |
| Comment by Githook User [ 10/Aug/18 ] |
|
Author: {'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}Message: |
| Comment by Githook User [ 10/Aug/18 ] |
|
Author: {'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}Message: |
| Comment by Max Hirschhorn [ 08/Aug/18 ] |
|
I don't think we should upload the unstripped binary when the dbtest task succeeds. Could we add a compile_dbtest Evergreen task to the compile_all_run_unittests_TG task group as well (similar to what we already do with the compile_unittests and unittests tasks), and then have a dbtest! display task to ensure the appropriate dependencies are selected? CC brian.samek |
| Comment by Jonathan Abrahams [ 08/Aug/18 ] |
|
max.hirschhorn The task_groups do not support dependencies, so this approach would mean a user could select dbtest and not compile and it would fail because the artifacts do not exist. We have to consider not stripping dbtest executable in compile. The unstripped dbtest is approximately 19 times larger (1.1 GB) than the stripped binary (58 MB) The compressed gzipped tar (408 GB) is about 18 times larger (22 MB). |
| Comment by Max Hirschhorn [ 10/Jul/18 ] |
|
We should add dbtest to the compile_all_run_unittests_TG task group and upload the binary (unstripped) if any dbtest test case fails. |