[SERVER-43611] a non-icecream build following an icecream build is not a no-op. Created: 24/Sep/19  Updated: 27/Oct/23  Resolved: 19/Dec/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gabriel Russell (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Development Platform
Operating System: ALL
Sprint: Dev Tools 2019-10-21, Dev Tools 2019-11-04, Dev Tools 2019-11-18, Dev Tools 2019-12-02, Dev Platform 2019-12-30
Participants:

 Description   

If you complete an icecream build, and then immediately do a non-icecream build results from the icecream build are not utilized



 Comments   
Comment by Andrew Morrow (Inactive) [ 19/Dec/19 ]

OK, I figured this out. This happens because we actually change compile flags when using icecream

        env.AppendUnique(
            CCFLAGS=[
                '-fdirectives-only'
            ]
        )

So this behavior is expected, even if not desirable.

Comment by Gabriel Russell (Inactive) [ 05/Dec/19 ]

acm On master, first I ran

./buildscripts/scons.py --variables-files=etc/scons/mongodbtoolchain_v3_gcc.vars  ICECC=/usr/bin/icecc VERBOSE=1 mongod

And followed it up with

./buildscripts/scons.py --variables-files=etc/scons/mongodbtoolchain_v3_gcc.vars VERBOSE=1 mongod

And it did a full rebuild in the second invocation.

Comment by Andrew Morrow (Inactive) [ 15/Oct/19 ]

Ping gabriel.russell - could you give this another try? I did revert some of the more recent changes to the tool so it is possible that it is back to a working state.

Comment by Andrew Morrow (Inactive) [ 11/Oct/19 ]

gabriel.russell - I wasn't able to reproduce this. Can you retry your test case and post your repro instructions? Were you using Ninja or plain SCons?

Generated at Thu Feb 08 05:03:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.