You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I think we can't use ~ in a path, as one normally can in a shell.
This means many paths need to be fully qualified, which binds a conf file to a very specific setup.
The problem is, we don't want expand the ~ too early and in the wrong place either, because then we end up with RunId objects not being the same anymore for the same path.
So, we could not compare across different machines. Generally, comparing between machines is done very rarely because it's not generally useful, but sometimes, we are indeed interested in the machines.
Currently, I think we can't use
~
in a path, as one normally can in a shell.This means many paths need to be fully qualified, which binds a conf file to a very specific setup.
The problem is, we don't want expand the
~
too early and in the wrong place either, because then we end up withRunId
objects not being the same anymore for the same path.So, we could not compare across different machines. Generally, comparing between machines is done very rarely because it's not generally useful, but sometimes, we are indeed interested in the machines.
So, a good point for the expansion might be here:
ReBench/rebench/model/run_id.py
Line 279 in 1de0e22
This bit was added allow iterations to be part of the command line, also with the goal to avoid breaking the
RunId
identity: #216The text was updated successfully, but these errors were encountered: