Mir

Use environment variables for supplying sockets in benchmark tools

Bug #1496803 reported by Nick Dedekind
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Triaged
Medium
Unassigned
mir (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Currently the benchmark tools (benchmarks/mir_perf_framework/client.py) in mir use the -f and -m command switches for supplying mir server sockets. Should use environment variables so that we can use binaries which do not parse these parameters.

See original description
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

AFAIK, this feature already exists for any Mir client: env MIR_SOCKET=...

Changed in mir:
status: New → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yep, it just works as it always has:

    env MIR_SOCKET=....

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

It's the benchmark tools, not the clients that need fixing

Changed in mir:
status: Invalid → Confirmed
description: updated
Changed in mir:
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.