cannot compile with release version of simfactory

Create issue
Issue #1643 closed
Roland Haas created an issue

I just tried to compile with the release version of simfactory (on Gordon but that would not matter) and I get:

[rhaas@gordon-ln1 Cactus]$ ./simfactory/bin/sim build --thornlist thornlists/
Error: required key email in section hal1 is missing
Aborting Simfactory.

The same happens for the "user" key as well.

This is most likely hidden for most users since keys in the [default] section of defs.ini.local hide this issue. email may make sense to specify in defs.local.ini but user would not seem like something that should be left to default since it is machine specific.


Comments (4)

  1. Frank Löffler
    • removed comment

    user and email are supposed to be defined in the default section of defs.local.ini. (Almost) none of the machines define these. Before you run simfactory the first time, you are either supposed to copy the example, or use "sim setup". Did you do one of the two? These should generate these entries.

    note: I was thrown off first because 'hal1' is one of my machines, and I suspected an error there. And while hal1 is one of the machines where it actually makes sense to specify a fixed user name (and because of that you don't get an error for a missing user name), I suspect the fact that 'hal1' is mentioned here might just be "bad luck".

    As for where to specify user: It does make sense to put it into [default] because a lot of users have the same user name on a large number of machines. Whenever this is not the case you have to put it (also) in machine specific sections of course...

  2. Roland Haas reporter
    • changed status to resolved
    • removed comment

    Uh, I did not. I tend to forget and then get confused by the error message which does not seem to point me to the right solution at all. I am not sure I agree that a "lot of users have the same user name on a large number of machines" but "some" may.

    I'll just chalk this up to simfactories UI/error handling being strange.

  3. Frank Löffler
    • removed comment

    It sure is strange. It should at least point to its state being unconfigured, or maybe use the local user name in that case (because most likely you want to build locally anyway when you didn't care about configuration).

  4. Log in to comment