1406006 - Build SHA1 incorrectly displayed when built in hg repository

Status: RESOLVED FIXED

(Testing :: geckodriver, defect, P3)

Description

[Andreas Tolfsen ❲:ato❳]

We compile in the SHA1 from which the geckodriver binary was built,
but it appears not to be working:

> 1507199756141	geckodriver	INFO	geckodriver 0.19.0 (0000000000000000000000000000000000000000 2017-10-04)

Comment 1

[Andreas Tolfsen ❲:ato❳]

It appears to work with git:

> % ./mach geckodriver 
>  0:00.41 /home/ato/src/gecko/obj-x86_64-pc-linux-gnu/dist/bin/geckodriver --binary /home/ato/src/gecko/obj-x86_64-pc-linux-gnu/dist/bin/firefox
> 1518457267636	geckodriver	INFO	geckodriver 0.19.1 (3ee38289dac8838fe848f7234d75f3cef5d3dbc7 2018-02-09)

Comment 2

[Andreas Tolfsen ❲:ato❳]

whimboo reported the following for hg:

> 1518458462131    geckodriver    INFO    geckodriver 0.19.1 ( '802cb5d2c482'  '2018-02-07 08:28 +0100')

This means the build SHA1 isn’t broken, but that it is incorrectly
displayed when building from hg.

Comment 3

[Andreas Tolfsen ❲:ato❳]

The problem here is that the build SHA1 inside the parenthesis
should not contain quotes.  I’m assuming hg returns them
with quotes and that we need to massage the output a bit in
testing/geckodriver/build.rs.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

It is returned correctly by `commit_hash()`, but maybe the `writeln!` macro adds those extra quotes?

Comment 5

[Andreas Tolfsen ❲:ato❳]

(In reply to Henrik Skupin (:whimboo) from comment #4)

> It is returned correctly by `commit_hash()`, but maybe the
> `writeln!` macro adds those extra quotes?

I think the output from hg must contain the quotes, considering we
write it correctly for git.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

What I did was to run the hg command as listed in build.rs, that's all. 

When I have a look at the generated build-info.rs file I see:

> const COMMIT_HASH: Option<&'static str> = Some(" \'802cb5d2c482\'");
> const COMMIT_DATE: Option<&'static str> = Some(" \'2018-02-07 08:28 +0100\'");

The output file contains:

> Output { status: ExitStatus(ExitStatus(0)), stdout: " \'38b3c1d03a59\'", stderr: "" }
> Output { status: ExitStatus(ExitStatus(0)), stdout: " \'2018-02-13 11:39 +0200\'", stderr: "" }

So it's something inside `exec` which puts the quotes around the strings.

Comment 7

[Jeremy Lempereur [:o0ignition0o]]

Attachment: Bug 1406006 - Get well formatted commit hash and commit date when building geckodriver.

Review commit: https://reviewboard.mozilla.org/r/251318/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/251318/

Comment 8

[Jeremy Lempereur [:o0ignition0o]]

Heya :) 

It turns out the hg log command -T flag doesn't require quotes or anything. 

The output is now : 

```
$ cargo run
   Compiling geckodriver v0.21.0 (file:///C:/Users/Ignition/Projects/mozilla/mozilla-unified/testing/geckodriver)
    Finished dev [optimized + debuginfo] target(s) in 26.51 secs
     Running `c:\Users\Ignition\Projects\mozilla\mozilla-unified\target\debug\geckodriver.exe`
1529221334142   geckodriver     INFO    geckodriver 0.21.0 (944187065098 2018-06-17 09:38 +0200)
1529221334192   geckodriver     INFO    Listening on 127.0.0.1:4444
```

Does it look good to you ?

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Thank you for the patch. I forwarded the review to Andreas, who is the mentor of this bug and can also reproduce it compared to me.

Comment 10

[Andreas Tolfsen ❲:ato❳]

Comment on attachment 8985821 [details]
Bug 1406006 - Get well formatted commit hash and commit date when building geckodriver.

https://reviewboard.mozilla.org/r/251318/#review257672

Comment 11

[Andreas Tolfsen ❲:ato❳]

Thanks for the patch!

Comment 12

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/4cdab1b804e8
Get well formatted commit hash and commit date when building geckodriver. r=ato

Comment 13

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/4cdab1b804e8