- Jun 09, 2023
-
-
Hans Fangohr authored
Not sure how this could get here.
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
Turned out I had an extra file in the directories (install.log) which then showed up as a microarchitecture.
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
-
Hans Fangohr authored
-
Ashwin Kumar Karnad authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Ashwin Kumar Karnad authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
-
Hans Fangohr authored
- in case of upcoming failure, this provides a clue in which function the failure is to find.
-
Hans Fangohr authored
-
Hans Fangohr authored
- it is only called once - easier to have the code of the function in the place where it is called now
-
- Jun 08, 2023
-
-
Hans Fangohr authored
-
Hans Fangohr authored
Motivation: - the actual command we run is pretty meaningless without context. - to provide the context, we would need to add additional 'logging.info' command BEFORE we call `run` - if we select loglevel `debug` we get to see the same output as before.
-