[SERVER-18897] unittests.txt may not have the right dependents Created: 09/Jun/15 Updated: 11/Jun/15 Resolved: 11/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Jonathan Reams |
| Resolution: | Done | Votes: | 0 |
| Labels: | build-jbr | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Build 5 06/26/16 |
| Participants: |
| Description |
|
If you build unittests.txt and then change your build command line such that the variant directory changes (by adding --ssl, for example), unittests.txt is not rebuilt and is left out-of-date. |
| Comments |
| Comment by Eric Milkie [ 11/Jun/15 ] |
|
Sorry, I figured out what went wrong. I was building the unit tests via their binary target, not the alias "unittests". This means that unittests.txt does not have the actual unit tests as dependents. I suppose this is correct, however, since unittests.txt requires that all unit tests are up-to-date, not just one particular one. |
| Comment by Eric Milkie [ 09/Jun/15 ] |
|
This is a bigger issue than it used to be, after we eliminated the "smokeCppUnittests" SConscript target. The replacement workflow is to do "scons unittests" and then run resmoke.py with suite=unittests, which uses unittests.txt to know what to run. |