Explicitly defines the kClockSystemTrace in the syscall parameters test

Explicitly defines the kClockSystemTrace in the syscall parameters test

TraceTicks is going away, so TraceTicks::kClockSystemTrace is also going
away.

If this test is to continue existing, it needs to define the clock ID
itself.

BUG=541692
Committed: https://crrev.com/bdcd6db1893a596f9454ae22e33f35541b6f240d
Cr-Commit-Position: refs/heads/master@{#357871}

[charliea (OOO until 10-5), 2015-11-04 13:40:30]

charliea@chromium.org changed reviewers:
+ rickyz@chromium.org

[charliea (OOO until 10-5), 2015-11-04 13:41:38]

On 2015/11/04 13:40:31, charliea wrote:

Hi Ricky,

If you'd prefer that I just kill this test altogether, just let me know. Now
that no clocks are powered by the system trace clock, it feels a little bit
arbitrary to test that it causes a crash, but you know a lot more about this
area than I do.

[charliea (OOO until 10-5), 2015-11-04 13:42:55]

Patchset #1 (id:1) has been deleted

[rickyz (no longer on Chrome), 2015-11-04 19:06:33]

Like I mentioned in chat, I'd probably lean towards just removing the fest
altogether - lgtm

[charliea (OOO until 10-5), 2015-11-04 19:06:45]

The CQ bit was checked by charliea@chromium.org

[commit-bot: I haz the power, 2015-11-04 19:07:26]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1423803003/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1423803003/40001

[commit-bot: I haz the power, 2015-11-04 19:25:26]

Committed patchset #2 (id:40001)

[commit-bot: I haz the power, 2015-11-04 19:26:20]

Patchset 2 (id:??) landed as
https://crrev.com/bdcd6db1893a596f9454ae22e33f35541b6f240d
Cr-Commit-Position: refs/heads/master@{#357871}