Håvard Berland

> But we write a lot of files in the run_path prior to running `job_dispatch.py`. So why isn't this caught earlier? These files are written by the master node, which...

Still occurs after merging #3428 : ```The target file:DESIGN_KW.OK has not been updated; this is flagged as failure. mtime:1654868393.0 stat_start_time:1654868393000000000```

This involves modifying the driver to query the queueing system for each individual job with `qstat -f ` and then parsing the output. From `man qstat` on an Azure-node: ```...

The driver can also be changed to *always* call `qstat` with the `-f` option, and pick the job status from this line: ``` qstat -x -f 4233 | grep job_state...

I think we should come up with a better name for the package "`protobuf`" in here. I would like protobuf to be an implementation detail, and not exposed in the...

Should we think more through the first values for Enums, as in `proto3` the default for enums will always be the first defined element. I am afraid this can be...

> But then we can change to `proto3` right away :), which I wanted to avoid, but maybe at least to reorder ... hm I suspect we might be stuck...

Noting a crash: ``` $ ert es_mda --enable-experiment-server poly.ert Experiment failed: Phase must be an integer between (inclusive) 0 and 2, got 3. ERT crashed unexpectedly with "Phase must be...

> Noting a crash: > > ``` > $ ert es_mda --enable-experiment-server poly.ert > Experiment failed: Phase must be an integer between (inclusive) 0 and 2, got 3. > ERT...

The file `tests/ert_tests/cli/test_integration_cli.py` has some experiment server tests at the end which assert on stdout. Should these be rewritten to assert on something smarter? (or it might not make sense...