Bug 1625281 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
OK, so `make -p` says:

```
# makefile (from 'backend.mk', line 12)
RUST_PROGRAMS = x86_64-pc-windows-msvc/release/updateagent.exe

x86_64-pc-windows-msvc/release/updateagent.exe: force-cargo-program-build

../../../dist/bin/updateagent.exe: x86_64-pc-windows-msvc/release/updateagent.exe x86_64-pc-windows-msvc/release/updateagent.exe
	$(install_targets_sanity)
	$(call install_cmd,$(IFLAGS2) '$<' '$(@D)')

target:: x86_64-pc-windows-msvc/release/updateagent.exe
target::
target:: ../../../dist/bin/updateagent.exe
```

which I believe is a correct dependency graph, since installing the updateagent in dist/bin/ depends on actually compiling the updateagent, which in turn depends on running cargo.  I don't see whether the failure in compiling the things but then not installing the thing is coming from...unless there are problems with timestamps of the actual files?

After a successful build, what does `ls -l --time=style=+%s.%N` on `dist/bin/updateagent.exe` and its corresponding file in `toolkit/components/updateagent` look like?  After an unsuccessful build, what do those timestamps look like?
Revision 1 by
on 
OK, so `make -p` says:

```
# makefile (from 'backend.mk', line 12)
RUST_PROGRAMS = x86_64-pc-windows-msvc/release/updateagent.exe

x86_64-pc-windows-msvc/release/updateagent.exe: force-cargo-program-build

../../../dist/bin/updateagent.exe: x86_64-pc-windows-msvc/release/updateagent.exe x86_64-pc-windows-msvc/release/updateagent.exe
	$(install_targets_sanity)
	$(call install_cmd,$(IFLAGS2) '$<' '$(@D)')

target:: x86_64-pc-windows-msvc/release/updateagent.exe
target::
target:: ../../../dist/bin/updateagent.exe
```

which I believe is a correct dependency graph, since installing the updateagent in dist/bin/ depends on actually compiling the updateagent, which in turn depends on running cargo.  I don't see where the failure in compiling the things but then not installing the thing is coming from...unless there are problems with timestamps of the actual files?

After a successful build, what does `ls -l --time=style=+%s.%N` on `dist/bin/updateagent.exe` and its corresponding file in `toolkit/components/updateagent` look like?  After an unsuccessful build, what do those timestamps look like?

Back to Bug 1625281 Comment 4